Two bridging stories landed in the same week of August 2026. The Sandbox halted bridging to Base and BNB Chain after an alleged unauthorised mint of a very large number of tokens, with the final damage still disputed. BounceBit announced it will sunset its own blockchain after a roughly 3 million dollar exploit and migrate to BNB Chain.
Different causes, one lesson: a bridge is a single point of failure that most users only notice on the day it fails.
Why bridges break the way they do
A canonical bridge is a contract that locks an asset on one chain and mints a claim on another. Everything depends on the mint being authorised by exactly the right thing — a proof, a multisig, a validator set — and on nothing else being able to call it. When that check fails, the mint is unbacked and the peg is gone.
The operational response is always the same: pause bridging. That is the correct response, and it is also why a pause is expensive. The wrapped asset on the far side stops being redeemable, the market prices in the doubt, and holders find that the exit they assumed existed is closed for as long as the investigation runs.
BounceBit’s case is the other failure mode. The exploit was survivable in dollars; the chain around it was not viable enough to justify rebuilding, so the project chose to move to an established chain rather than keep operating its own. Users of a sunsetting chain face the same practical problem as users of a paused bridge — a migration window, an official route and a deadline.
What to do when your exit is closed
Do not chase an off-peg wrapped asset. A wrapped token trading below par after a mint incident is priced for a real probability that redemption never opens. Buying it is a bet on the investigation, not a discount.
Use the official migration path if the team publishes one. A sunsetting project usually contracts a specific route with specific dates. That path is supported; anything else is you improvising with your own funds.
Verify the announcement at the source. Bridge incidents attract impostor accounts within minutes. Read the project’s own channel, then check that any contract address in the message matches the one the project has used before. Our note on vetting a service before you send applies verbatim to a migration contract.
Know the second route. If you hold the native asset on a chain that still works, a non-custodial exchange is a different mechanism from a bridge: it is a swap into a genuinely different asset with its own liquidity, not a claim against a locked balance. When BNB is trading normally and a wrapper is not, the exchanger route is open and the bridge is not.
The structural point
Bridges concentrate risk. One contract holds the collateral for every user of that route, so an error is total rather than proportional. A swap through an exchanger concentrates a different and smaller risk: your single order, for the minutes it takes to settle, against a counterparty you chose.
That is not an argument that exchangers are safe and bridges are not. It is an argument for not having one exit. The pairs we track exist across several routes precisely because the cheapest route on a calm day and the available route on a bad day are frequently not the same one.
FAQ
Is wrapped SAND on Base safe to hold right now?
Treat any wrapped asset whose bridge is paused as unredeemable until the project confirms otherwise. Its market price already reflects that uncertainty.
What happens to my tokens when a chain sunsets?
The team normally publishes a migration contract and a deadline. Assets not migrated before the deadline can be stranded, so the date matters more than the mechanism.
Does a bridge halt affect exchange rates for the native asset?
Usually yes, briefly. Reserves fall on services that used that bridge to rebalance, spreads widen, and both recover once an alternative route is in use.
How do I check whether a route is live before sending?
Open the direction page for the pair. If a service is quoting with a fresh timestamp and a reserve above your amount, the route is live for that size.