Bridges have lost more user funds than any other category in crypto. Over a billion dollars has gone in bridge exploits, which makes "which bridge is cheapest" the wrong first question. The right one is: which bridge minimises what I have to trust?
Here is how the major bridges actually work, which ones have the strongest security models, and what to use for the routes people actually take.
The short answer
- Moving USDC: Circle CCTP, always — you get native USDC, never a wrapped IOU.
- Fastest with the best security record: deBridge — $9B+ moved, zero exploits.
- Easiest for beginners: Jumper — compares every bridge and picks the best route for you.
- Best for L2-to-L2: Hop or Orbiter.
- Best for intent-based speed: Across.
Why bridges get hacked
Most bridges work by locking your asset on the source chain and minting a wrapped representation on the destination. That lock contract accumulates enormous value — and becomes a honeypot. If it is compromised, every wrapped token backed by it becomes worthless simultaneously.
This is the structural flaw behind the largest bridge exploits. It is why the security model matters far more than the fee, and why the newer designs deliberately avoid pooled lock contracts.
The security models, ranked
Native burn-and-mint (strongest)
Circle CCTP is the clearest example. When you move USDC, it is burned on the source chain and Circle mints genuine, canonical USDC on the destination. There is no wrapped IOU and no honeypot contract. You end up holding real USDC, issued by the same entity that issues all USDC.
The trust assumption is Circle itself — but that is the same assumption you already accept by holding USDC at all. This is why virtually every major bridge and aggregator now routes USDC through CCTP under the hood. For stablecoin transfers, nothing else comes close.
Intent-based / solver networks (very strong)
deBridge and Across use a fundamentally different design: independent solvers fill your order on the destination chain from their own capital, then get reimbursed. There is no large pooled liquidity contract sitting as a target.
deBridge has processed over $9 billion with zero exploits, which in this category is a genuinely notable claim. Both settle fast — often under a minute. This model has become the preferred design for good reason.
Decentralised validator networks (strong, with caveats)
Axelar is a proof-of-stake blockchain whose job is connecting other chains, with a decentralised validator set verifying messages. Chainlink CCIP layers an independent Risk Management Network on top of its oracle network specifically to catch anomalous cross-chain activity — a defence-in-depth design aimed at institutional use.
The trust assumption is validator honesty backed by stake. That is meaningfully better than a small multisig, but it is not the same as cryptographic guarantees.
Liquidity pools (weakest structurally)
Synapse, Celer cBridge, and similar designs hold pooled liquidity on each chain. They work well, are widely used, and Celer in particular has an extensive audit history across 40+ chains. But the pooled model is the one with the worst historical track record when things go wrong.
Aggregators: the practical answer for most people
You do not have to pick a bridge yourself. Aggregators scan many bridges and DEXs simultaneously and route your transfer through whatever gives the best quote at that moment.
Jumper (built on LI.FI) is the most beginner-friendly: pick source and destination, and it handles route selection across 50+ chains. Bungee (on Socket) is a strong alternative with a useful refuel feature that sends you a little destination-chain gas alongside your assets — which solves the classic problem of bridging funds to a chain where you cannot afford to transact.
The honest caveat: an aggregator's security is inherited from whichever bridge it routes through. They add route selection and monitoring, but they do not eliminate the underlying risk. What they do eliminate is you accidentally picking a bad bridge on a route you have never used.
What to use for common routes
- USDC anywhere → anywhere: CCTP, via Jumper or directly.
- Ethereum L2 → L2 (Arbitrum, Optimism, Base): Hop bypasses the multi-day native withdrawal wait. Orbiter is cheaper and covers newer zk-rollups like zkSync, Starknet, and Linea.
- Large transfers where security dominates: deBridge or CCTP.
- Into Cosmos: Squid, built on Axelar's messaging.
- Involving Bitcoin: Symbiosis covers 30+ networks including BTC.
- You are not sure: Jumper, and let it decide.
Rules that will save you money
- Always test with a small amount first on any new route. Always. The cost of a test transfer is trivial against the cost of discovering a problem with your full balance.
- Check what you receive, not just what you send. If a bridge hands you a wrapped token rather than the canonical asset, you are holding an IOU whose value depends on that bridge remaining solvent.
- Do not leave large balances mid-bridge. Bridge, verify, move on.
- Make sure you have destination gas. Bridging your entire balance to a chain where you cannot pay for a transaction is a genuinely common and infuriating mistake — Bungee's refuel exists precisely because of it.
- Compare total cost, not headline fee. Bridge fee plus gas on both sides plus slippage is the real number.
The uncomfortable truth
Bridging is the riskiest routine action in crypto. Every bridge, including the best ones here, carries smart contract risk that a same-chain swap does not. The security models have improved enormously — intent-based designs and native burn-and-mint are real advances over the lock-and-wrap era — but the risk has not gone to zero.
The practical implication: bridge what you need, when you need it, and do not treat cross-chain positions as somewhere to park capital indefinitely.
Tools referenced in this article
- All cross-chain bridges — full category with 19 bridges and aggregators reviewed
- Circle CCTP, deBridge, Across
- Jumper, Bungee, LI.FI
- Hop, Orbiter, Axelar