Bridge (Cross-Chain)

How Bridges Work

The most common bridge architecture is lock-and-mint: a user deposits tokens into a smart contract on the source chain, and the bridge protocol mints an equivalent amount of wrapped tokens on the destination chain. When the user wants to return, they burn the wrapped tokens and the original assets are unlocked. For example, bridging USDC from Ethereum to Arbitrum locks USDC on Ethereum and mints bridged USDC on Arbitrum.

Liquidity-based bridges operate differently. Instead of locking and minting, they maintain liquidity pools on both chains. A user deposits tokens on one side and a liquidity provider releases tokens on the other side. This model, used by protocols like Across and Stargate, is faster because it does not require waiting for finality on the source chain, but it depends on sufficient liquidity being available.

Native bridges are built directly into the Layer-2 protocol. Arbitrum, Optimism, and Base each have canonical bridges that move assets between Ethereum mainnet and their respective L2 networks. These native bridges are the most secure option but are typically slower (withdrawals from optimistic rollups take 7 days to finalize) than third-party bridge protocols.

Why Bridges Matter

Bridges are essential infrastructure for a multi-chain DeFi ecosystem. Without bridges, assets on one chain are completely isolated from opportunities on another. A trader holding ETH on mainnet cannot participate in a Solana token launch, and a user with SOL cannot supply liquidity on Arbitrum, unless bridges connect these networks.

However, bridges are also among the highest-risk components in crypto. They hold large pools of locked assets, making them prime targets for hackers. The Ronin bridge ($625M), Wormhole ($320M), and Nomad ($190M) exploits demonstrate the security challenges. Traders should use established bridges, verify contract addresses, and avoid bridging more than necessary. Native L2 bridges and battle-tested protocols like Across and Stargate have the strongest security track records.

Real-World Example

A trader holds USDC on Ethereum mainnet but wants to trade a new token on Base. They use the Base native bridge to send USDC from Ethereum to Base. The bridge contract locks their USDC on Ethereum and the Base sequencer credits USDC to their address on Base. The deposit takes approximately 10-15 minutes. Alternatively, they could use a third-party bridge like Across, which uses liquidity providers to deliver USDC on Base within 1-2 minutes at a small fee (0.05-0.1%). After trading, they can bridge profits back to Ethereum or another chain.