Lab: free tools · size first · stock scanner · crypto scanner · journal

Infrastructure

Cross-Chain Bridge

A cross-chain bridge is a protocol that moves tokens, data or messages between two separate blockchain networks. It typically locks assets on the source chain, mints wrapped representations on the destination chain, and provides a trust mechanism (federated multisig, light client verification, or optimistic challenge periods) to validate transfers across the chain boundary.

A cross-chain bridge moves assets or messages between blockchains that cannot natively see each other. Most lock or burn tokens on one chain and mint or release them on the other, and the security of that hand-off is where the risk sits.

Blockchains are sovereign systems. Ethereum does not natively know what is happening on Solana, and Bitcoin cannot verify state on Polygon. Each chain maintains its own validator set, consensus rules, and state machine. That makes direct cross-chain asset transfers impossible at the protocol layer without external infrastructure. Cross-chain bridges fill this gap by acting as relay infrastructure: they observe events on one chain and trigger corresponding actions on another.

The most common bridge architecture is lock-and-mint. When a user bridges 1 ETH from Ethereum to Arbitrum, the ETH is locked in a smart contract on Ethereum, and a "wrapped" representation (WETH on Arbitrum) is minted on the destination chain. The original ETH remains locked as collateral backing the wrapped asset. When the user bridges back, the wrapped asset is burned and the original ETH is unlocked.

Burn-and-mint bridges avoid holding a central pool of locked assets by instead burning the native token on the source chain and minting a new equivalent on the destination chain. This requires the token to be natively multi-chain (issued on multiple chains simultaneously) and a trusted minter contract on each chain. Circle's Cross-Chain Transfer Protocol (CCTP) for USDC uses this model: USDC is burned on the source chain and natively minted on the destination chain by Circle's attestation service, eliminating the risk of a locked collateral pool being drained.

Canonical bridges are officially operated by the Layer 2 protocol itself. Arbitrum's canonical bridge, Optimism's Standard Bridge, and zkSync's native bridge are examples. They are considered the most trust-minimised option because their security derives from the same fraud proofs or validity proofs that secure the Layer 2 itself. The trade-off is speed: canonical bridges for optimistic rollups have a 7-day withdrawal delay corresponding to the fraud proof challenge window.

Third-party bridges such as Stargate, Across, Hop, and Synapse offer faster cross-chain transfers by using their own liquidity pools and validator/oracle networks, bypassing the 7-day delay. These bridges provide better UX but introduce additional trust assumptions: you are trusting the bridge's oracle network, validator set, or relayer infrastructure in addition to the underlying chains. Their security budgets are also much smaller than the underlying L1/L2 protocols, making them more vulnerable to economic attacks.

First-generation bridges moved only tokens. The next evolution is generalised message passing: bridging arbitrary data and smart contract calls between chains. LayerZero, Axelar, Wormhole (post-hack, rebuilt with a new architecture), and Chainlink CCIP (Cross-Chain Interoperability Protocol) are leading generalised messaging protocols.