/ How crypto bridges work
A crypto bridge moves value between blockchains that can't natively communicate. There are three dominant designs. Lock-and-mint bridges lock an asset on the source chain and mint a wrapped representation on the destination; canonical L2 bridges (the official Arbitrum or Optimism bridges) do this with the security of the underlying rollup. Liquidity-network bridges hold pools on both sides and pay you out of the destination pool, avoiding wrapped assets but introducing liquidity risk. Messaging layers like LayerZero and Wormhole provide the generic cross-chain communication that many bridges and apps are built on top of.
The trust model is the whole game. A bridge is only as secure as the entity verifying that the source-chain event really happened — that might be a multisig, a set of external validators, an optimistic challenge window, or a light-client proof. Every bridge exploit in history traces back to a weakness in that verification layer, not the smart-contract code that moves the tokens. Understanding who attests to your transfer is more important than the advertised fee or speed.
/ Comparing bridges on fees, speed, and coverage
Bridge cost is the sum of the source-chain gas, the destination-chain gas, and the bridge's own fee or spread. Liquidity-network bridges typically quote an all-in output amount that bakes in the spread, while messaging-based bridges charge a relayer fee on top of gas. Speed ranges from a few seconds for liquidity bridges and fast messaging layers to seven days for an optimistic-rollup canonical withdrawal — a gap that matters enormously depending on whether you're moving working capital or doing a one-time migration.
Chain coverage determines whether the bridge can even serve your route. Aggregators like LI.FI sidestep this by routing across many underlying bridges and picking the best path for your specific pair, combining a swap and a bridge into one transaction. For a single well-supported route, a direct bridge is often cheaper; for an obscure pair, an aggregator usually wins on both price and reliability.
/ Bridge security — the highest-risk surface in Web3
Bridges have lost more user funds to exploits than any other category in crypto — the Ronin, Wormhole, and Nomad incidents alone account for over a billion dollars combined. The recurring failure mode is compromise of the validation layer: a stolen multisig key, a forged signature set, or a logic bug that lets an attacker mint destination assets without locking source assets. This is why the trust model deserves more scrutiny than any other attribute.
Practical defense: prefer canonical bridges for L2 transfers when speed isn't critical, prefer battle-tested messaging layers and aggregators with strong audit and incident histories for everything else, and never bridge more than you're willing to lose in a single transfer. Split very large transfers, verify the destination address obsessively, and treat any brand-new bridge with extreme caution regardless of its incentive program. Our individual reviews document each bridge's exploit history and current security posture.
/ Which bridge should you use?
For moving in and out of an L2 where you can wait, the canonical bridge is the safest option. For fast, flexible cross-chain transfers, a well-audited aggregator like LI.FI gives you the best route across many underlying bridges while abstracting the complexity. Messaging layers like LayerZero and Wormhole are the infrastructure most modern bridges and cross-chain apps depend on — understanding them helps you assess the apps built on top.
Use the comparison table to shortlist by chain support and architecture, then read the security history in each review before moving size. The dedicated bridge comparison pages resolve the most common routes and the overall ranking.