BounceBit retires its Layer‑1 chain and reissues BB on BNB Chain after a token authorization flaw

BounceBit announced the retirement of its standalone Layer‑1 network after an authorization flaw allowed the movement of about 286.5 million BB tokens from nine accounts. The company will reissue BB on BNB Chain with a 1:1 balance reconstruction for holders.

What happened

The flaw stemmed from protocol‑level authorization logic inherited from the Evmos stack. It let a caller designate another account as the funding source without the required approval, though private keys, signatures and wallets were not compromised.

Migration details

Balances are being transferred using block 20,697,260 (timestamp 21:02:35 UTC, Aug 19) as the cutoff. Addresses holding at least 10 BB at the snapshot will automatically receive the same amount on the new BNB‑Chain contract; smaller balances will be claimable later. Staked and unbonding BB are included, even though the original chain no longer produces blocks.

Impact on token utility

Before the shutdown BB served five roles: proof‑of‑stake participation, validator rewards, gas, platform currency/composability, and on‑chain governance. BounceBit has not disclosed one‑for‑one replacements for any of these functions. The new token will initially operate within BounceBit’s existing BNB‑Chain DeFi products (CeDeFi V4, Prime, Strategy, RWA, and Promo vaults), with broader utility to be defined in a future roadmap.

Exchange considerations

Exchanges that hold BB must reconcile the snapshot with their internal ledgers. BounceBit is working directly with exchanges, but trading, deposits and withdrawals will resume only after each venue completes its due‑diligence and announces a timeline.

Open questions

• How will BB‑tokens, stBB, vault receipts, rewards and redemption paths be represented after the old ledger is abandoned?
• When will the new contract address be disclosed and distribution completed?
• What concrete economic roles will the migrated BB token assume on BNB Chain?