What is a canonical bridge?
- Author
- CRYPTO PORT Editorial
- Published
- Updated
- Reading time
- 5 min
In short
A canonical bridge is the official deposit and withdrawal path built into the layer 2 protocol itself. It locks assets on layer 1 and issues the matching amount on layer 2, with no third-party operator in between. You trust fewer parties, but withdrawals take the protocol's waiting period.
Key points
- The official deposit and withdrawal path built into the L2 protocol
- Locks assets on L1 and issues the same amount on L2
- Fewer trust assumptions because no third party sits in the middle
- Withdrawals require the protocol's waiting period
Definition
A bridge defined as part of the layer 2 protocol itself: assets are deposited into a layer 1 contract, and the corresponding token is minted and burned on layer 2.
To deposit, you send assets to a bridge contract on layer 1; that fact is relayed to layer 2, where the same amount is minted. Withdrawing is the reverse: the token is burned on layer 2, and the locked funds on layer 1 are released once the proof or challenge process completes.
What differs from a third-party bridge is who you trust. A canonical bridge only assumes the layer 2's own contracts and proving system are sound — no external multisig or validator set enters the picture. The layer 2's own admin keys, however, remain part of the assumption.
Tokens with the same name are not interchangeable across bridges. USDC that arrived via the canonical bridge and USDC from a third-party bridge have different contract addresses and may not trade against each other on a DEX. Check which route a token came through before you transact.
Watch out for
- · Even a canonical bridge leaves the risk that admin keys on the layer 2 alter the contracts
- · Withdrawals wait for challenge windows or proofs, and that cannot be shortened when the market moves
- · Identically named tokens from different bridges have different addresses and may not be swappable