Crypto Bridges: Moving Assets Between Chains, and the Risks That Come With It

What a Bridge Does

Blockchains are isolated by design. A Bitcoin transaction cannot reference Ethereum state. An Ethereum smart contract cannot read Solana balances. Each chain is its own sealed universe. A bridge is infrastructure that connects two chains, letting assets effectively move between them even though no blockchain can directly transfer data to another.

The problem matters because liquidity and applications fragment across chains. If you want to use a protocol on Arbitrum but your USDC is on Ethereum, you need a bridge. If a DeFi position on Solana is best hedged through an Ethereum-based derivative, you need a bridge. Bridges are the plumbing of multi-chain crypto.

Bridge Architectures

Lock-and-Mint

The user sends assets to a bridge contract on the source chain. The bridge locks those assets in custody. On the destination chain, the bridge mints a wrapped representation of the asset. When the user wants to go back, they burn the wrapped asset on the destination and unlock the original on the source.

This is how Wrapped BTC (WBTC) on Ethereum works. The underlying BTC sits in BitGo custody. Each WBTC on Ethereum represents 1 BTC held in that custody.

Tradeoffs:

• Simple to understand
• Requires trust that the custody holds the locked assets
• Wrapped tokens are not fungible with natively-issued ones

Burn-and-Mint

The user burns tokens on the source chain (destroys them). The bridge verifies the burn and mints new tokens on the destination chain. No locked custody is required because the asset genuinely moves; burning on one chain is equivalent to creating on the other.

Circle's CCTP (Cross-Chain Transfer Protocol) works this way for USDC. USDC on Ethereum is burned; new USDC is minted natively on the destination chain. The result is natively-issued USDC on both sides rather than wrapped representations.

Liquidity Network Bridges

Instead of locking assets, liquidity networks maintain pools on each supported chain. The user swaps asset A on chain 1 for asset A on chain 2 by trading against the bridge's liquidity pool on each side. Arbitrageurs and market makers keep the two pools balanced.

Examples: Across, Stargate, Synapse, Hop Protocol.

Tradeoffs:

• Fast (no cross-chain verification delay)
• Liquidity-dependent (large transfers can slip)
• Economic incentives for pool operators must keep flow balanced

The Messaging Layer

Modern bridges increasingly separate the asset-transfer logic from the cross-chain messaging infrastructure. A messaging protocol can pass arbitrary data (including asset-transfer instructions) between chains. Bridges, cross-chain DeFi protocols, and general interoperability tools build on top of these messaging layers.

Each model has different trust assumptions. Guardian networks trust a fixed validator set. Oracle-based models trust specific oracles. Light-client-based models (IBC) require running verification code on each connected chain but provide the strongest guarantees.

Why Bridges Are the Largest Hack Category

Bridges are attractive targets because they concentrate value. A single bridge holds millions to billions of dollars of locked assets. A single exploit drains the entire contract. Compared to individual wallets or smaller DeFi positions, bridges offer the highest return per compromise.

Bridge architecture tends to create complex trust assumptions: validator sets, multisigs, oracle dependencies, cross-chain proof verification. Any link in the chain can be exploited. Simpler designs (native issuer bridges, light-client bridges) have smaller attack surfaces but are harder to build across arbitrary chains.

Native Issuer Bridges

For stablecoins, the safest bridge is often the native issuer's own cross-chain protocol:

• USDC: Circle's CCTP burns USDC on source, mints on destination. No wrapped tokens.
• USDT: Tether mints natively on most chains. Cross-chain transfers use Tether's own infrastructure.

Using these removes the wrapped-token depeg risk and the bridge-exploit risk that affects third-party bridges. For large stablecoin transfers, they're usually the recommended path.

Bridging Safely

Questions to ask before bridging:

1. Is the asset available natively on both chains? USDC is natively issued on many chains via CCTP. Using CCTP avoids wrapped-token risk.
2. How large is the bridge's total value locked? Larger bridges have more scrutiny but also hold more at risk. Smaller bridges can be safer for small amounts but may concentrate risk for large ones.
3. What's the security model? Validator sets, multisigs, light clients, and oracles all have different tradeoffs. Light-client bridges (IBC) are the strongest; multisig-based bridges are the weakest.
4. Has the bridge been audited and battle-tested? New bridges are higher risk. Established bridges with years of operation have more catches and fewer unknown bugs.
5. How fast is the bridge? Some bridges settle in minutes; others take hours. For volatile assets or time-sensitive trades, latency matters.

For small amounts, convenience often wins. For large amounts, use native issuer bridges where available and limit third-party bridge exposure to what you can afford to lose.

Related Intelligence

• Layer 1 vs Layer 2: How L2 canonical bridges work and why they're different from generic bridges.
• Smart Contracts: The code bridges run on, and the main attack surface for exploits.
• Stablecoins: Native stablecoin bridges (like Circle CCTP) are often the safest path.