Most bridge losses are not failures of cryptography. They are category errors. A user believes they hold a claim on a rollup and actually hold a claim on a company, or believes a route is official because it is the one their wallet offered first. The three products below look identical in a balance and behave nothing alike when something breaks.
Product one: the canonical bridge
The canonical bridge is part of the rollup’s own contracts. You deposit into a contract on Ethereum, the rollup credits you on its own ledger, and to leave you submit a withdrawal that the rollup’s proof or challenge process has to clear.
The keys here belong to the rollup, not to a company. An optimistic rollup releases your withdrawal after its challenge window closes, which is why Ethereum.org’s L2 directory in October 2026 shows Base and OP Mainnet at 7 days to mainnet and Arbitrum’s dispute window at 45,818 blocks, about 6.4 days. A ZK rollup proves the state instead of waiting, and ZKsync Era quotes a 3-hour minimum in the same October 2026 Ethereum.org listing.
What you receive is a native claim. If the rollup is live and its contracts have not been upgraded into something else, that claim is enforceable on mainnet without anyone’s permission.
Product two: the liquidity network
A third-party bridge is a market maker with inventory on both sides. You send funds to its contract on one chain, and it pays you from its pool on the other, usually within minutes.
The keys are the network’s contracts and its treasury. Nothing here waits for the rollup, which is precisely the product: the pool absorbs the wait and prices it into a spread or a fee. You receive the native asset, but it arrives because a business decided to send it, not because a proof cleared.
This is not automatically worse. It is faster, it works across chains that share no settlement layer, and for small amounts the spread can undercut a canonical exit. What it is not is canonical.
FeeEdge’s survey of 17 August 2026 priced these routes differently by chain, with Solana under $0.01, Base at under $0.01 to $0.10, Arbitrum at $0.01 to $0.50, Tron at $1 to $3, and Bitcoin at $0.50 to $5 and above. The spread across chains is a liquidity fact, not a safety signal.
Product three: the wrapped-asset issuer
The third product issues a token that represents a claim on an asset held somewhere else. You hold a symbol, and behind it sit a custodian, a redemption desk, and a legal agreement.
The keys are the issuer’s mint authority and its custody arrangement. What you receive is an IOU. It trades like the underlying, until you want the underlying, at which point the redemption process applies. That process involves identity checks at most issuers, a queue, and often a minimum size.
The failure mode is not a smart contract bug. It is the issuer stopping, the custody going wrong, or the redemption terms changing while you hold the token.
| Product | Who holds the keys | What you actually hold | Clock to exit |
|---|---|---|---|
| Canonical rollup bridge | The rollup’s contracts and its proof or challenge rule | A native claim enforceable on mainnet | 7 days on Base and OP Mainnet, about 6.4 days on Arbitrum, 3 hours minimum on ZKsync Era, per Ethereum.org in October 2026 |
| Third-party liquidity network | The network’s contracts and its inventory | A transfer paid from a pool | Minutes, because the pool carries the wait |
| Wrapped-asset issuer | The issuer’s mint authority and custodian | An IOU redeemable through the issuer | Redemption queue plus identity checks at most issuers |
| Exchange withdrawal | The venue | A credit on the venue’s ledger | Venue policy, not a chain rule |
Four questions before you move size
What claim do I hold? Native, pooled, or issued. If the answer is not native, you have a counterparty. Know its name.
Who can stop me? Find the key that can pause, freeze, upgrade or blacklist. A bridge whose contracts can be upgraded by a multisig is a bridge with an operator, whatever the documentation says.
What is the exit clock, and who pays for it? A 7-day canonical exit, the Ethereum.org figure for Base and OP Mainnet in October 2026, is free of counterparty risk and expensive in time. A minutes-long pooled exit is the reverse. Both are prices, and only one of them appears in the fee.
What happens if the operator stops? For a native claim, nothing. For a pool, your transfer stops. For an issuer, redemption becomes a legal process with an unknown timeline.
Verdict
Only the canonical bridge gives you a claim on the rollup itself. The other two give you a claim on a business, and businesses are useful, fast, and occasionally gone.
Size accordingly. Move small amounts through the fast routes and pay the spread. Move size through the route whose failure mode you have read, and check the exit clock first.
Start with what a sequencer does to see who produces the state your claim depends on, then check the DeFi section for how those claims get reused once they land.
0 comments
No comments yet — ask a question and we will answer it here.