Other system
BounceBit ticker BB
Historical network. Its profile describes the design as history. The evidence is in the system note below.
Summary
Until August 2026 BounceBit Chain was a proof-of-stake chain built from BounceBit's forks of Evmos's Cosmos SDK and of CometBFT, running an EVM through the bbcored node. Validators bonded BB, holders delegated to them, and a block committed once validators holding more than two-thirds of voting power signed it. Early docs described dual-token staking, with half of 50 validator slots for BTC stakers, but later docs say BBTC node staking and stBBTC were retired in V3, leaving BB as the only staking asset. BTC and dollars reached the chain as tokens backed by assets held by custodians such as Ceffu, never through Bitcoin-verified proofs. After an attacker abused a built-in vesting module inherited from Evmos, BounceBit halted the chain on 20 August 2026 and sunset it. No consensus runs today. 126811122833
Design
- System
- Other systemBounceBit Chain no longer runs. It was a proof-of-stake layer 1 built from BounceBit's forks of Evmos's Cosmos SDK and of CometBFT, with an EVM (EVM chain ID 6001, Cosmos chain ID bouncebit_6001-1). After an exploit on 19 and 20 August 2026, block production stopped at height 20,702,857, and on 21 August BounceBit said it would permanently sunset the chain and reissue BB as a BEP-20 token on BNB Chain. The package listed it as a layer 1; because the chain has shut down it uses the other class, and the design is described as history.
- Settlement family
- Cosmos SDK
- Scarce resource
- Stake (proof of stake)
- State model
- Accounts
- Finality
- Economic finality
- Who makes blocks
- While the chain ran, validators in the active set proposed blocks. The docs describe 24-hour epochs in which the active set was chosen by voting weight from staked BB, with the maximum size set by governance; an older staking page describes 50 validators. CometBFT rotates the proposer in proportion to voting power. The size of the set at the halt was not verified. A January 2026 post announced a move to Clique proof of authority, where a known set of signers produces blocks; no activation was found, and the Evmos-based design was still running when it was exploited.
- Fork choice
- No open fork choice: each height was decided when validators with more than two-thirds of voting power precommitted, so committed blocks were not reorganised in normal operation, and the chain stopped rather than forked if more than a third went offline. The end was an operator decision: production was halted at height 20,702,857 on 20 August 2026, and BounceBit took balances for the reissued BB from an earlier block, 20,697,260, so transfers in the roughly 5,600 committed blocks between them, including the attacker's, were not carried over.
Qualifications
- Live chain status · Not applicable. An attacker moved about 286.5 million BB from nine accounts between 21:02 UTC on 19 August and 01:54 UTC on 20 August 2026, through an authorization flaw in a vesting module inherited from Evmos. Block production stopped at height 20,702,857 at 02:36 UTC on 20 August, and on 21 August BounceBit said it would permanently sunset the chain. On 27 September 2026 its website and docs still described the chain as its settlement layer, with no notice. Block time, fees and validator details describe how the chain ran.
- Holder migration · Partial. BounceBit reissued BB as a BEP-20 token on BNB Smart Chain, 1:1 against balances at block 20,697,260 (21:02:35 UTC, 19 August 2026), just before the first unauthorized transfer. Later transactions, including the 286.5 million BB the attacker moved, were not carried over. Reports say balances of 10 BB or more go automatically to the same address on BNB Chain and smaller ones to a later claim portal. How BB-tokens and staked positions on the chain are settled was not confirmed.
- Bitcoin backed security · Contested. BounceBit was marketed as BTC restaking with dual-token proof of stake, and its website still says so. But BTC was never locked on Bitcoin under rules the chain verified: BBTC was a token backed by custodied or bridged BTC, and the V3 docs say BBTC node staking and stBBTC were no longer offered. Bitcoin never checked BounceBit's state.
- Settlement family · Partial. The chain was built on forks of Evmos's Cosmos SDK and of CometBFT, but users saw an EVM environment: 0x addresses, MetaMask and Solidity contracts. It settled to neither Ethereum nor Bitcoin, and BB now lives on BNB Smart Chain, a separate network. Use of Cosmos inter-chain messaging was not found in the docs reviewed.
- Block time · Not applicable. No blocks are produced. The January 2026 Ignition post announced 0.5-second blocks, which were not observed. The reported snapshot and halt heights are about 5,600 blocks and five and a half hours apart, which works out to roughly 3.6 seconds per block just before the halt; that is arithmetic from reported figures, not a measurement.
- Announced consensus change · Not applicable. The January 2026 Ignition post described Clique proof of authority, EIP-1559 fees and a 30 million gas limit, and promised a separate operator post. No activation or operator post was found, the August 2026 exploit hit the Evmos-based design that was still running, and the chain was then sunset.
- Node source availability · Partial. BounceBit publishes its forks of the Cosmos SDK, CometBFT and go-ethereum code, and its node repository holds guides, network files and a release list, but no repository for the bbcored application itself was found. Release notes are one-line summaries.
- Throughput · Not applicable. The chain no longer processes transactions. The Ignition post gave transfer-rate figures derived for a proof-of-authority configuration that never ran, so no throughput claim is recorded.
Tradeoffs
- Emphasizes
- Security and Scalability Contested
- Gives up
- Decentralization and continuity. Consensus was limited to a governance-capped validator set on 32 GB machines, no public source code for the node application was found, and the BTC and dollar assets the chain was built around were claims on custodians, not coins it could verify. In August 2026 an inherited software flaw let an attacker move about 286.5 million BB; BounceBit halted the chain, chose the snapshot for rebuilt balances and moved BB to BNB Chain, decisions holders could not override.BounceBit marketed BTC restaking as a security source; that reading is contested, since Bitcoin never checked the chain. The security corner here covers only the chain's own ledger while it ran: the two-thirds commit rule and slashing. It never covered the backing of BBTC, BBUSD or other BB-tokens, which rests on custodians such as Ceffu, and the August 2026 exploit came from flawed permission checks in module logic, not from breaking consensus. The scalability reading follows the EVM design and the Ignition plan, which never activated; no throughput figure was verified.
- Full node at home
- Not applicable 122425There is no live BounceBit Chain to follow: block production stopped on 20 August 2026 and BounceBit said the chain would be permanently sunset. While it ran, the full-node guide linked from the mainnet setup page suggested 8 physical cores (16 vCPUs), 32 GB of RAM and a 500 GB NVMe drive; that guide was written for testnet, and the mainnet service file capped node memory at 27 GB. The setup page still lists a mainnet archive snapshot dated 2 August 2026 and no shutdown notice.
- Throughput claims
- No classified figure recorded
Scaling layers
No scaling layer recorded in this profile.
Capabilities
| Capability | How it is provided | Notes and sources |
|---|---|---|
| Account abstraction | Structured assessment pending | Not yet assessed for any chain. |
| Atomic swaps | Not present | No swap can settle on BounceBit Chain, which has executed no transactions since the August 2026 halt. While it ran, EVM contracts could have implemented hash- and time-locked swaps, which are building blocks only, but no BounceBit-documented swap mechanism or deployment was found. 2 |
| Authenticated data publication | Unknown | Not yet assessed under this row's current definition. |
| Light clients | Unknown | Not yet assessed under the current definitions; No new state can be verified after the halt. While the chain ran, CometBFT supported light-client verification in general, but no BounceBit light client or compact verification path was documented. |
| Native staking or delegation | Structured assessment pending | Not yet assessed for any chain. |
| On-chain governance | Structured assessment pending | Not yet assessed for any chain. |
| Parallel execution | Structured assessment pending | Not yet assessed for any chain. |
| Payment or state channels | Unknown | No source was cited for absence, so the rule that absence needs a source makes this unknown. The earlier review found no payment or state channel layer anchored to BounceBit Chain in the reviewed docs, and none can operate on a halted chain. |
| Programmable spending | None found Earlier definition | Nothing can execute since the halt. While the chain ran, it had an EVM with Solidity contracts, and node release v1.5.4 removed the deployment allow-list so any address could deploy. Contracts could also call built-in modules; the permission flaw exploited in August 2026 sat on that contract path. 2927 |
| Protocol-verified messaging | Structured assessment pending | Not yet assessed for any chain. |
| Reversible transfers or recovery | Not present | No payment can be cancelled, delayed or recovered on BounceBit Chain, which has executed no transactions since the August 2026 halt; while it ran, no user feature for this was found. BounceBit could pause BB-token transfers for incident response, only vault contracts could mint or burn them, and after the exploit it rebuilt BB balances on BNB Chain from a pre-attack snapshot. Those are operator actions on holders, not a feature holders could set up. 2719 |
| Rollups | Unknown | Absence before the halt was not verified, so the rule that absence needs a source makes this unknown. The earlier review found no rollup settling to BounceBit Chain; the docs' shared security clients were a restaking concept tied to BTC staking, which was later retired, and are not rollups. 1220 |
| Shielded transfers | Structured assessment pending | Not yet assessed for any chain. |
| Signed partial offers | Unknown | Not yet assessed under this row's current definition. |
Reading these values
- How this feature is provided
- Built into the protocol, core-team software or independent software says where a feature lives and who can change it. These are implementation layers, not quality: core-team software is not closer to the protocol than independent software.
- Structured assessment pending
- The shared review has not assessed this feature for any chain yet (Account abstraction, Native staking or delegation, On-chain governance, Parallel execution, Protocol-verified messaging and Shielded transfers). That does not mean it is absent, and a chain’s profile may already describe it.
- Unknown
- The review has not established this for this chain under the current definition; the note beside it says why. Unknown is not absent and not a low score. A feature reads “Not present” only when a source shows it is absent.
- Earlier definition
- Payment or state channels, Programmable spending and Rollups keep the earlier definition until the next fact-check. There, “Native” does not separate the protocol from core-team software, “Ecosystem software” does not say who publishes it, and “Partial” does not say which layer.
- Reading across rows
- The list of capabilities is incomplete. Do not read these rows as a chain leading or lagging overall.
Ecosystem & custody
| Product type | Status | Notes and sources |
|---|---|---|
| Automated market makers | None foundBitswap (BounceClub swap, inactive) | No exchange can operate on the halted chain. BounceBit's BounceClub docs describe its own constant-product swap, Bitswap, and a Bitswap v3 SDK repository was updated in March 2026. At review, club.bouncebit.io opened BounceBit's strategy app instead of a swap. 2212228 |
| Issuer-native stablecoins | None found | No stablecoin can move on the halted chain, and no issuer listed BounceBit: neither Circle's USDC list nor Tether's protocol list includes it. BBUSD, BounceBit's own token for dollars placed with its custodial vaults, was a vault receipt that rebased weekly in V3, not an issuer-backed stablecoin. BBUSD tokens also exist on BNB Smart Chain and Ethereum. 1318343537 |
| Algorithmic stablecoins | None found | No stablecoin of any design can operate on the halted chain. The BounceClub docs describe CUSD, minted against BBTC collateral, which was collateral-backed rather than algorithmic; its supply was not measured. 23 |
| Bridges | None found | No bridge transfer to or from BounceBit Chain can complete after the halt. While it ran, most assets arrived through BounceBit's Portal: users deposited with a custodian program and BB-tokens were minted on the chain, which BounceBit called bridgeless. BB moved to Ethereum through LayerZero's OFT standard, and the docs also describe a BTC bridge approved by more than half of validators and a MultiBit route; the V3 notes say some bridges were retired. The move of BB to BNB Chain was a snapshot reissue, not a bridge. Risk: BB-tokens depend on the custodians, gateways and mint controllers behind them, and redemptions ran weekly; how positions minted on the stopped chain are settled was not confirmed. BB bridged to Ethereum relied on LayerZero's configuration, and its status after the reissue was not found. None of these routes was verified by Bitcoin. 461415161718 |
| Block explorers | First-partyBounceBit Explorer (explorer.bouncebit.io) | BounceBit's own explorer; bbscan.io and bbvision.io redirect to it. On 27 September 2026 the page loaded, but its block data could not be read in this review. It is the operator's record of a stopped chain, not independent confirmation, and no independent explorer was found. 1029 |
| Hardware wallets | ThinTrezor (BB listing; BounceBit network through MetaMask or Rabby) | See the custody rows: Trezor's BounceBit page lists BB on BNB Smart Chain and on the BounceBit network with MetaMask and Rabby, while Ledger's asset service and wallet code show no BounceBit network or BB coin. BB itself now lives as a BEP-20 token on BNB Smart Chain, and the BounceBit network no longer produces blocks. 2363739 |
Hardware-wallet custody
| Device maker | Status | What users can and cannot do |
|---|---|---|
| Ledger | UnknownSame as native: Unknown | Cannot: Find BounceBit Chain in Ledger's network list or in Ledger Wallet's open-source EVM network configuration Cannot: Treat Ledger-listed BBTC or BBUSD tokens on BNB Smart Chain or Ethereum as BounceBit Chain custodyLedger coin pages tried for BounceBit returned not found. Ledger's asset service lists BBTC and BBUSD as tokens on BNB Smart Chain, BBUSD on Ethereum, and a Solana token named BounceBit Token whose link to BounceBit was not verified; it showed no BB entry on BNB Smart Chain. Ledger does not say BounceBit is unsupported, and signing through MetaMask was not verified. 373839 |
| Trezor | Through an intermediaryMetaMask or Rabby, listed on Trezor's BounceBit pageSame as native: Unknown | Can: Keep the key for a BounceBit Chain address on a Trezor Safe 3, Safe 5 or Safe 7 and connect it to MetaMask or Rabby, which Trezor's BounceBit page lists beside the BounceBit network Can: Hold the reissued BB, a BEP-20 token on BNB Smart Chain, with Trezor Suite, MetaMask or Rabby; that is a token on another chain, not custody on BounceBit Chain Cannot: Send or receive on BounceBit Chain: it stopped producing blocks on 20 August 2026 and BounceBit has sunset it Cannot: Open BounceBit Chain accounts in Trezor Suite: the page does not say which app handles which network, and no Trezor source shows Suite supporting the BounceBit networkTrezor's page still lists the BounceBit network after the shutdown. Holding BB on BNB Smart Chain is holding a token on another chain, not custody on BounceBit Chain. Older Trezor models are not listed. 2536 |
Public data
iKnow Blockchain has no public-data lookups for BounceBit yet. This is a limit of the service, not a statement about the network.
| Lookup | Status | What it covers and its limits |
|---|---|---|
| Address or account | Not available yet | Public-data lookups for this chain are not built yet. |
| Tokens and assets | Not available yet | Public-data lookups for this chain are not built yet. |
| NFTs | Not available yet | Public-data lookups for this chain are not built yet. |
| Transactions | Not available yet | Public-data lookups for this chain are not built yet. |
Sourced developments
Developments: Review overdue Reviewed Sep 27, 2026; next review was due Oct 7, 2026, 12:00 UTC.
Publication date · newest first
-
BB reissued on BNB Smart Chain; Bitget completes its 1:1 swap
BB was reissued 1:1 as a BEP-20 token on BNB Smart Chain against balances at block 20,697,260. Reports of BounceBit's plan say addresses holding 10 BB or more receive it automatically at the same address, with smaller balances left for a later claim portal. Bitget announced its 1:1 swap on 1 September 2026 and said on 2 September that the swap was complete and BEP-20 BB deposits and withdrawals had reopened.
- Implementation:reissued BB deployed on BNB Smart Chain
- Release:exchange swaps announced 1 September and completed at Bitget on 2 September 2026
- Activation:automatic distribution reported; completion for every eligible address and the small-balance claim portal not confirmed
Sources: Bitget — Bitget Will Support the BounceBit (BB) Contract Swap (external site) · Bitget — Bitget Has Completed the BounceBit (BB) Contract Swap (external site) · CryptoSlate — Chain shutdown strips BounceBit token utility after authorization flaw exposes 286M tokens (external site) · Crowdfund Insider — Bitcoin Restaking Platform BounceBit To Wind Down L1 Blockchain Following Exploit (external site)
-
BounceBit halts its chain after an exploit and says it will permanently sunset it
Between 21:02 UTC on 19 August and 01:54 UTC on 20 August 2026, an attacker used an authorization flaw in a vesting module inherited from Evmos to move about 286.5 million BB from nine accounts. Block production stopped at height 20,702,857 at 02:36 UTC on 20 August. On 21 August BounceBit said it would permanently sunset BounceBit Chain and reissue BB as a BEP-20 token on BNB Chain, using balances from block 20,697,260, just before the first unauthorized transfer.
- Implementation:block production halted at height 20,702,857 on 20 August 2026
- Release:announced by BounceBit on X; no notice on its website, docs, blog or Medium feed at review
- Activation:chain stopped; permanent sunset announced 21 August 2026
Sources: The Block — BounceBit to sunset blockchain, migrate to BNB Chain after $3 million exploit (external site) · Crypto Briefing — BounceBit shuts down chain after attacker moves 286.5 million BB (external site) · Crowdfund Insider — Bitcoin Restaking Platform BounceBit To Wind Down L1 Blockchain Following Exploit (external site) · BounceBit — BounceBit Blog (external site) · BounceBit — BounceBit posts on Medium (feed) (external site) · BounceBit — BounceBit website (external site)
-
BounceBit announced the Ignition chain upgrade with proof of authority and 0.5-second blocks
BounceBit announced Ignition, a chain upgrade that would use the Clique proof-of-authority engine with 0.5-second blocks, EIP-1559 fees, a 30 million gas limit and RPC limits, to prepare for a perpetual-futures product. The post promised a separate operator post and gave no activation date.
- Proposal:announced by BounceBit
- Implementation:no activation found
- Release:no matching node release found; newest listed release is v1.6.2 from February 2025
- Activation:not activated before the chain was halted in August 2026
Sources: BounceBit — The Chain Upgrade That Raises BounceBit's Ceiling: Ignition (external site) · BounceBit Labs — bouncebit-chain-node releases (external site) · Crypto Briefing — BounceBit shuts down chain after attacker moves 286.5 million BB (external site)
-
BounceBit Prime added Standard Chartered custody with OKX collateral mirroring
BounceBit announced that Prime's tokenised Treasury strategies would pair custody at Standard Chartered with trading on OKX, where collateral is mirrored to the exchange instead of being deposited there.
- Implementation:described as live by BounceBit
- Release:announced 3 November 2025
- Activation:not independently verified
Sources: BounceBit — BounceBit, OKX and Standard Chartered Expand Institutional Access to Tokenized U.S. Treasury Yield Strategies via Collateral Mirroring Program (external site) · BounceBit — Architecture (external site) · BounceBit — BounceBit Prime introduction (external site)
Topics your AI can explain
Your AI can explain these topics for BounceBit through the connection, with sources.
Known gaps
What this profile's review did not establish:
- BounceBit's own announcements of the exploit, the sunset and the reissue were posts on X, which could not be read directly. The details here come from news reports (The Block, Crypto Briefing, Crowdfund Insider, CryptoSlate) and Bitget's exchange notices. BounceBit's blog, Medium feed, docs and website showed no notice on 27 September 2026.
- How BB-tokens such as BBTC and BBUSD, stBB and staked or unbonding positions on the stopped chain were settled or moved was not confirmed.
- Whether the claim portal for balances under 10 BB has opened, and whether automatic distribution to all eligible addresses finished, was not confirmed.
- The status of BB bridged to Ethereum through LayerZero after the reissue was not found.
- The halt and snapshot heights come from news reports of BounceBit's announcement; the explorer's block data could not be read in this review.
- The final active validator count, validator cap, slashing parameters and unbonding period were not verified. The docs give 7 days and 24 hours in different places for unstaking.
- The source code of the bbcored node application was not found; only forks of upstream libraries, guides and release notes are public.
- When V3 retired BBTC node staking was not dated in the sources reviewed.
- Whether the Ignition upgrade was ever deployed on a test network was not confirmed; the operator post it promised was not found.
- Custodian reserve reports and attestations were not reviewed, and governance procedures and past proposals were not reviewed.
- Third-party hardware-wallet signing paths, such as a Ledger through MetaMask on a custom network, were not tested.
Sources
Oldest dated source check: Source checked Sep 27, 2026 Next check due Oct 27, 2026.
- BounceBit to sunset blockchain, migrate to BNB Chain after $3 million exploit (external site)
- BounceBit shuts down chain after attacker moves 286.5 million BB (external site)
- Bitcoin Restaking Platform BounceBit To Wind Down L1 Blockchain Following Exploit (external site)
- Chain shutdown strips BounceBit token utility after authorization flaw exposes 286M tokens (external site)
- Bitget Has Completed the BounceBit (BB) Contract Swap (external site)
- Architecture (external site)
- CeDeFi introduction (external site)
- Consensus Mechanism (listed under the deprecated BounceBit Chain section) (external site)
- EVM Compatibility & Alignment (external site)
- Chain Info (external site)
- Staking Delegation (external site)
- [Deprecated] Liquid Staking (stBB) (external site)
- Stablecoins on BounceBit (BBUSD) (external site)
- Liquid Custody (external site)
- BTC Bridge (external site)
- [Deprecated] Bread and Butter (BB Cross-chain Liquidity) (external site)
- MultiBit Bridge (external site)
- [Deprecated] V3 FAQ (external site)
- [Deprecated] BB-Token Standard (V3) (external site)
- Shared Security Clients (external site)
- BounceClub Intro (external site)
- Bitswap (archived BounceClub member guide) (external site)
- BounceClub V2 Stablecoin (external site)
- BounceBit Mainnet Node Setup (external site)
- Running a Full Node (external site)
- Become a Validator (external site)
- bouncebit-chain-node releases (external site)
- BounceBit-Labs on GitHub (external site)
- BounceBit Explorer (external site)
- BounceBit posts on Medium (feed; includes the Ignition chain upgrade post of 16 January 2026) (external site)
- BounceBit Blog (external site)
- BounceBit website (external site)
- Byzantine Consensus Algorithm (external site)
- USDC contract addresses (external site)
- Supported protocols (external site)
- BounceBit wallet (external site)
- Ledger crypto-asset service: token search for BounceBit (external site)
- Ledger crypto-asset service, network list (external site)
- Ledger Live EVM network configuration (families/evm/config.ts) (external site)
- Chain 6001 (BounceBit Mainnet) record (external site)
Report an error
Found something wrong or out of date? Reporting is free, and every chain goes through the same process. Published corrections appear in the public log.
Funding disclosure
Funding disclosures appear here when an upkeep arrangement exists, in the form “Upkeep funded by [name]; verdicts unaffected.” The funder ledger has not been published yet. Neutrality & funding