What is a Crypto Bridge?

Cross-chain bridges are the infrastructure that connects separate blockchain networks, allowing users to move assets and data between chains. As the blockchain ecosystem has expanded across Ethereum, Layer 2 networks, Solana, Cosmos, and dozens of other chains, bridges have become essential for accessing DeFi opportunities, moving liquidity, and participating in multi-chain ecosystems. However, bridges are also the most-attacked infrastructure in crypto, with over $2.5 billion stolen in bridge hacks. This guide explains how bridges work, the different types, major bridges, security risks, and how to use them safely.

What is a Cross-Chain Bridge?

A cross-chain bridge is a protocol that enables the transfer of assets, data, or messages between two or more blockchain networks. Each blockchain is an isolated system with its own consensus, state, and rules. Bridges create a connection between these isolated systems.

The fundamental challenge is that blockchains cannot natively read each other's state. Ethereum has no way to verify what happened on Solana, and vice versa. Bridges solve this by implementing various verification mechanisms to prove that an action occurred on one chain before executing a corresponding action on another.

Cross-Chain Bridge Flow:

  Ethereum                   Bridge                    Arbitrum
  ┌──────────┐            ┌──────────┐            ┌──────────┐
  │          │  Lock ETH  │          │  Mint ETH  │          │
  │  User    │───────────>│  Bridge  │───────────>│  User    │
  │  has ETH │            │  Contract│            │  has ETH │
  │  on L1   │            │          │            │  on L2   │
  └──────────┘            └──────────┘            └──────────┘

  To bridge back:
  ┌──────────┐            ┌──────────┐            ┌──────────┐
  │          │  Burn ETH  │          │ Unlock ETH │          │
  │  User    │───────────>│  Bridge  │───────────>│  User    │
  │  has ETH │            │  Contract│            │  has ETH │
  │  on L2   │            │          │            │  on L1   │
  └──────────┘            └──────────┘            └──────────┘

Types of Cross-Chain Bridges

Bridges use different mechanisms to move assets between chains. Each approach has distinct security properties and trade-offs:

Lock-and-Mint

The most common bridge mechanism. The user locks their tokens in a smart contract on the source chain, and the bridge mints an equivalent "wrapped" representation on the destination chain. To bridge back, the wrapped tokens are burned, and the originals are unlocked. Examples: Wormhole, Polygon PoS Bridge.

Burn-and-Mint

Used when the token issuer controls minting on multiple chains. Instead of locking tokens, they are burned on the source chain and freshly minted on the destination chain. There is no pool of locked tokens to attack. Circle's CCTP (Cross-Chain Transfer Protocol) for USDC is the prime example: USDC is burned on one chain and natively minted on another.

Liquidity Pool Bridges

Instead of lock-and-mint, these bridges maintain liquidity pools of native tokens on both chains. When a user wants to bridge, they deposit tokens into the pool on the source chain and receive tokens from the pool on the destination chain. This approach avoids wrapped tokens entirely. Examples: Stargate, Across Protocol, Hop Protocol.

Message Passing Bridges

Rather than just moving tokens, these bridges enable arbitrary cross-chain communication. Smart contracts on one chain can call functions on contracts on another chain. This unlocks cross-chain DeFi, governance, and complex multi-chain applications. Examples: LayerZero, Chainlink CCIP, Axelar, Hyperlane.

Canonical (Native) Bridges

These are the official bridges built by L2 teams as part of their rollup infrastructure. They inherit the security of the underlying L1 (Ethereum) and do not require additional trust assumptions beyond the rollup itself. Examples: Arbitrum Bridge, Optimism Bridge, zkSync Bridge, Polygon zkEVM Bridge.

Major Cross-Chain Bridges

Bridge Security Risks and Major Hacks

Cross-chain bridges are the most-attacked category of smart contracts in crypto. The reason is simple: bridges hold massive amounts of locked tokens, and their cross-chain verification logic is inherently complex. A single vulnerability can drain hundreds of millions of dollars.

Notable Bridge Hacks

Trust Assumptions Comparison

Every bridge makes trust assumptions about who verifies cross-chain messages. These assumptions determine the security model:

How to Use Bridges Safely

Given the significant risks, here are best practices for using cross-chain bridges:

1. Use canonical bridges when possible: For Ethereum to L2 transfers, the official rollup bridge is the most secure option. It inherits Ethereum's security guarantees.
2. Start with small test amounts: Before bridging a significant amount, send a small test transaction first. Verify it arrives correctly on the destination chain.
3. Check bridge TVL and track record: Established bridges with high TVL and long track records without incidents are generally safer. Check DeFiLlama for TVL data.
4. Verify the bridge URL: Phishing sites mimicking popular bridges are common. Bookmark official URLs and always verify you are on the correct domain.
5. Use bridge aggregators: Tools like LI.FI, Socket, and Bungee compare routes across multiple bridges to find the best rates and safest paths.
6. Avoid bridging more than necessary: Keep the minimum amount needed on each chain. If a bridge gets exploited, your exposure is limited to what you have bridged.
7. Prefer native tokens: When possible, use bridges that deliver native tokens (via liquidity pools or burn-and-mint) rather than wrapped tokens. Native USDC via CCTP is safer than wrapped USDC via a lock-and-mint bridge.

The Future: Intent-Based and ZK Bridges

Bridge technology is rapidly evolving to address security and UX challenges:

• Intent-based bridges: Instead of users directly interacting with bridge contracts, they express an "intent" (I want 1 ETH on Arbitrum) and professional solvers compete to fill it. This abstracts away the bridging complexity. Examples: Across Protocol, UniswapX cross-chain.
• ZK-verified bridges: Zero-knowledge proofs can cryptographically verify that a transaction occurred on the source chain without trusting any external validators. This is the highest possible security model for bridges (trustless verification). Projects like zkBridge and Polymer Labs are developing this approach.
• Chain abstraction: The ultimate goal is to make bridging invisible to users. Instead of manually bridging assets, wallets and dApps will automatically route transactions across chains. The user simply interacts with an application, and the infrastructure handles cross-chain movement behind the scenes.

Frequently Asked Questions