BounceBit Chain Shutdown: Snapshot Set, Reissue on BNB Chain

The BounceBit blockchain has been frozen since August 20, 2026. Its operators say they will not restart it. The token, BB, is to be reissued as a BEP-20 token on BNB Chain. For anyone holding BB, the only number that matters is the snapshot block: 20,697,260.

A snapshot is a fixed record of every account balance at one precise moment. Whatever sat at an address in that block counts as the claim. Whatever moved a second later is invisible to the reissue. At BounceBit the snapshot was taken immediately before the first unauthorised transaction, which means the attacker's 286.5 million stolen BB will not be included in the new supply.

The exploit hit the Evmos stack, a ready-made blockchain kit. A flaw allowed a contract call to name someone else's account as the source of funds without checking that the account had agreed. Fourteen transactions from nine accounts drained roughly 286.5 million BB, worth about $3 million to $3.3 million at the time. No user keys or individual wallets were compromised, Protos reported. The fault sat in the protocol layer.

Rather than patch and keep running, the operators chose the hard cut. The chain stays off. BB is reissued as a BEP-20 token on BNB Chain. No reissue timetable has been announced yet. That is unusual and uncomfortable for holders, because an open-ended wait is harder to monitor than a hard deadline.

The snapshot block sits at 20,697,260. The chain kept running for about five and a half hours after that block, up to block 20,702,857. Anyone who bought, sold, transferred or deposited BB into a contract inside that window gets the balance from before it. A sale confirmed on the chain during that window can become retroactively ineffective. A deposit can equally come to nothing. In a chain shutdown, confirmed no longer means final.

A simple rule of conduct follows: as soon as a chain anywhere stands still or a team announces a halt, hands off that token until the cut-off date has been named publicly. Every movement in the unresolved window is a risk with nothing on the other side.

Staked holdings and those in the unbonding period are also to flow into the reissue, the operators said. These positions are tied to an address and can be read out cleanly. An open trade on an exchange, by contrast, sits in the provider's books rather than at your address, and is allocated by the exchange itself.

Where you keep your coins decides how much work comes your way. If the tokens sit at an exchange, the provider handles the migration. That is convenient but you depend on their timetable. You often cannot trade or withdraw during the changeover. Check the balance against your own record from the cut-off date once it is done.

If the tokens sit in a software wallet, an automatic distribution to the same address usually runs smoothly. You only have to add the target chain and enter the new contract. Take contract addresses exclusively from the project's official announcement. Migrations are the favourite occasion for fake contracts.

If the tokens sit on a hardware wallet, the same applies. The key stays offline, and you can add the target chain in the accompanying software without ever exporting the key. One drawback is device support, since not every hardware wallet carries every target chain.

Document your holding as of the cut-off date before anything is switched over. A screenshot of the wallet balance, the address in plain text and the block height are enough. If the distribution later deviates, that is your only evidence.

Chain shutdowns rarely come out of nowhere. Signals include: the core team goes quiet, the chain's validator count drops, token price falls steadily, development activity stops, and withdrawals from the chain's DeFi applications accelerate. When several appear together, it is time to review your position.

Three episodes from recent history show the pattern. ICON was an orderly case: an announced shutdown with a swap into a successor token and clearly named deadlines. The TON bridge shutdown showed a variant where a bridge between two chains was closed, not a chain itself. Harmony was a rollback, where the chain kept running but a snapshot taken before the exploit was used to restore balances. The BounceBit case is different: the chain ends, and the claim moves to another network.

The most expensive mistakes almost always come from haste. The first mistake is the panic move inside the unresolved window. As long as no cut-off date has been named, every transaction with the affected token is a blind flight. The second mistake is the wrong contract address. Around every migration, fake tokens with identical names appear. The third mistake is blind trust in the exchange. Without your own note from the cut-off date you cannot prove a discrepancy. The fourth mistake is ignoring the withdrawal freeze. Anyone who leaves the token at the exchange until the very last day loses the option of self-custody the moment withdrawals close.

No timetable has been set for the reissue. Holders of BB should actively watch the project's announcements and their exchange's notices. The case is small in market terms – BB's market cap sits around $4.18 million – but the mechanics apply to any future shutdown.

(As of August 23, 2026. This article is not investment advice.)