A canonical bridge is the official set of contracts a rollup designates for moving assets between itself and Ethereum. It’s built directly on top of the rollup’s own security — its fraud proof or validity proof mechanism — rather than relying on a separate operator’s own custody or multisig to vouch for the transfer.
That’s the distinction from a third-party bridge: a canonical bridge inherits whatever security guarantees the rollup itself has already earned, while a third-party bridge adds its own, separate set of trust assumptions (its own validator set, multisig, or oracle design) on top.
Why it matters
“Canonical” describes the trust model, not a guarantee of safety by itself — canonical bridges are still smart contracts, and smart contract bugs, upgrade-key compromises, and the rollup’s own sequencer or proof-system risk all still apply. What a canonical bridge removes is the extra, independent layer of trust a third-party bridge operator would otherwise add. Withdrawals through an optimistic rollup’s canonical bridge still wait out the challenge window; that’s the rollup’s security, not a bridge defect.
Example
A user deposits ETH into a rollup’s canonical bridge contract on L1; the deposit is reflected on the L2 once the rollup’s bridge logic processes it, and withdrawing back later follows the same contract pairing in reverse, subject to the rollup’s normal exit rules.
Related · Rollups
Not financial advice.