BounceBit to shut down its Layer 1 after $3 million exploit, migrate to BNB Chain
Security & Exploits ·
An authorization flaw allowed an attacker to drain 286.5 million BB tokens, prompting the project to abandon its standalone blockchain entirely.
BounceBit will sunset its own Layer 1 blockchain and move operations to BNB Chain following a $3 million exploit that saw an attacker steal 286.5 million BB tokens, according to The Block. The theft was traced to an authorization flaw in the project's infrastructure, though further technical detail on how the flaw was exploited has not been disclosed.
The decision to shut down the chain rather than patch and continue is notable given how heavy a lift standing up a Layer 1 is in the first place. Operating a base blockchain means running an independent validator set, native consensus rules, and a dedicated security budget rather than borrowing security from an existing network — infrastructure that took resources to build and is now being discarded in favor of migrating to BNB Chain's established settlement layer.
Multiple accounts of the incident converge on the same core figures: a $3 million loss and 286.5 million BB tokens taken, with the sunset-and-migrate plan confirmed across the reporting. The consistency of the numbers across sources points to a single, well-documented incident rather than a disputed or partial account.
Moving to BNB Chain effectively means BounceBit will give up the "hard parts" that define a Layer 1 — its own consensus, settlement, and native security — in exchange for relying on BNB Chain's existing validator network and security guarantees. That tradeoff removes the attack surface tied to running independent infrastructure but also cedes the autonomy that came with operating a sovereign base layer.
Unresolved so far are the precise mechanics of the authorization flaw, whether any funds have been recovered or frozen, and what timeline BounceBit has set for completing the migration and compensating affected holders of the stolen BB tokens. It also remains to be seen whether other projects running custom Layer 1s take this episode as a cue to reassess the security tradeoffs of maintaining independent chains versus building atop larger, established networks.