Canonical vs. Liquidity Bridges

What you'll learn

• Two Categories, Two Tradeoffs
• Canonical Bridges: Optimistic Rollups
• Canonical Bridges: ZK-Rollups and Validity Proofs
• Liquidity Bridges: Across, Stargate, Hop, Synapse, Connext
• Burn-and-Mint Bridges as a Canonical Alternative
• Choosing the Right Bridge Route

Key terms

Canonical bridge

A bridge operated by the chain itself (or its core team) and using native verification with the settlement layer. Typically the strongest trust model but with longer withdrawal times.

Liquidity bridge

A third-party bridge using pre-funded liquidity pools on each chain. Relayers front destination-chain funds for fast UX and later reimburse from the canonical bridge over the slow path.

Challenge period (rollup)

The 7-day window during which fraud proofs against optimistic-rollup state roots can be submitted. Withdrawals through the canonical bridge wait out this period before finalization.

Validity proof

A SNARK or STARK that mathematically proves a rollup's state transition was executed correctly. Used by ZK-rollups (zkSync, StarkNet, Linea, Scroll, Polygon zkEVM) for canonical-bridge finalization in hours rather than 7 days.

Stage 0 / 1 / 2

L2BEAT's classification of rollup decentralization. Stage 0 has training wheels (team can override). Stage 1 has limited training wheels with security council and timelocks. Stage 2 has no team override; protocol enforces all rules.

Fault proof

A challenge that any party can submit to dispute an invalid optimistic-rollup state root during the challenge window. Arbitrum BoLD and OP Stack fault proofs are the production examples as of 2024-2026.

Bonder (Hop Protocol)

In Hop, the party that bonds destination-chain native asset against an incoming hToken transfer, taking the time risk of canonical-bridge reimbursement in exchange for a fee.

Everclear (formerly Connext)

A modular interchain clearing layer that nets cross-chain settlements across multiple bridges, batching the slow onchain transfers while providing fast UX. The rebrand reflected the pivot from single-bridge to multi-source clearing.

Native asset (vs. wrapped)

On a destination chain, "native" means the asset is issued or authorized directly by the issuer (e.g., Circle USDC on every chain). "Wrapped" means the asset is a representation backed by a locked original on the source chain (e.g., older USDC.e).

Fast Transfer (CCTP V2)

CCTP V2 feature in which pre-funded liquidity providers front the destination-chain USDC against an in-flight attestation, achieving seconds-latency native USDC transfers between chains.