15 services rated

Best Cross-Chain Bridges

Bridges ranked on trust assumptions, exploit history and settlement speed.Every score below is the weighted mean of the rubric marks, not an editor's gut feel.

How we score this category

Full methodology →
Trust assumptions
Who or what must behave honestly for your funds to arrive, and how many of them there are.
30%
Exploit history
Losses to date, the class of failure involved, and whether the same failure remains possible.
25%
Settlement speed
Real time to finality across common routes, including worst-case delays.
15%
Chain coverage
Networks connected and whether liquidity on each route is genuinely available.
15%
Cost
Bridge fee, relayer cost and the spread on the asset you receive.
15%
8.9
Rank 1 · Strong

Relayers front you the funds in seconds and take the settlement risk themselves, secured by an optimistic oracle rather than a multisig.

Trust assumptions
8.5
Exploit history
9.5
Settlement speed
9.5
Chain coverage
8.0
Cost
9.0
8.9
Rank 2 · Strong

Burns USDC on one chain and mints it on another, so nothing is ever locked in a bridge contract waiting to be stolen.

Trust assumptions
8.0
Exploit history
10.0
Settlement speed
8.5
Chain coverage
8.0
Cost
10.0
8.9
Rank 3 · Strong

The only widely used bridge that verifies the other chain's consensus directly instead of asking a committee to vouch for it.

Trust assumptions
9.5
Exploit history
9.5
Settlement speed
8.5
Chain coverage
6.5
Cost
9.5
8.5
Rank 4 · Strong

An intent-based design where market makers fill your order from existing liquidity — no locked pool, no wrapped token.

Trust assumptions
7.5
Exploit history
9.5
Settlement speed
9.5
Chain coverage
8.0
Cost
8.5
8.3
Rank 5 · Strong

Bonders front liquidity against canonical settlement, giving you rollup speed with the canonical bridge underneath.

Trust assumptions
8.0
Exploit history
9.5
Settlement speed
9.0
Chain coverage
6.5
Cost
8.0
8.1
Rank 6 · Strong

Anyone can deploy it to any chain and choose their own security module — flexible, honest about the trade-off, and only as safe as your configuration.

Trust assumptions
7.0
Exploit history
9.5
Settlement speed
8.0
Chain coverage
8.0
Cost
8.0
8.0
Rank 7 · Strong

Connects more chains than anything else, with a configurable security model that applications routinely configure badly.

Trust assumptions
6.5
Exploit history
8.5
Settlement speed
8.5
Chain coverage
10.0
Cost
7.5
7.9
Rank 8 · Solid

A proof-of-stake chain doing the validating, which is more accountable than a signing committee and slower than everything else.

Trust assumptions
7.5
Exploit history
9.0
Settlement speed
7.0
Chain coverage
8.5
Cost
7.0
7.9
Rank 9 · Solid

The only bridge with a separate network whose sole job is to veto suspicious transfers — deliberate, expensive, and unbroken so far.

Trust assumptions
7.5
Exploit history
10.0
Settlement speed
7.0
Chain coverage
7.5
Cost
6.5
7.9
Rank 10 · Solid

The cheapest way between rollups, run by market makers you are trusting to deliver on the other side.

Trust assumptions
6.0
Exploit history
9.0
Settlement speed
9.0
Chain coverage
7.0
Cost
9.5
7.9
Rank 11 · Solid

Delivers native assets rather than wrappers from deep unified pools, on top of LayerZero's configurable trust model.

Trust assumptions
6.5
Exploit history
9.0
Settlement speed
8.5
Chain coverage
8.5
Cost
7.5
7.7
Rank 12 · Solid

A well-built router on top of Axelar, which means it inherits Axelar's security and adds its own contract layer.

Trust assumptions
7.0
Exploit history
9.0
Settlement speed
7.0
Chain coverage
8.0
Cost
7.0
7.6
Rank 13 · Solid

A long-running liquidity bridge with a broad chain list and an optimistic validation model that asks you to trust its validators.

Trust assumptions
6.0
Exploit history
8.5
Settlement speed
8.0
Chain coverage
8.5
Cost
8.0
7.2
Rank 14 · Solid

Cheap and widely deployed, with a 2022 DNS hijack that redirected users to a malicious front end.

Trust assumptions
6.0
Exploit history
6.5
Settlement speed
8.0
Chain coverage
8.5
Cost
8.5
7.0
Rank 15 · Solid

Rebuilt itself after a $325m signature-verification failure and has run cleanly since — on a nineteen-signer guardian model you must trust.

Trust assumptions
6.0
Exploit history
5.0
Settlement speed
8.5
Chain coverage
9.5
Cost
8.0

How OBOL rates bridges

Bridges have lost more money than any other category in crypto — well over two billion dollars across the sector's history. That is why trust assumptions carry the heaviest weight in this rubric. The question is not whether a bridge is decentralised in its marketing, but exactly whose signature, key or honesty stands between you and your funds.

Exploit history is weighted almost as heavily, and we look at the class of failure. A validator key compromise says something different about an operator than a signature verification bug does, and a protocol that has fixed one specific bug has not necessarily fixed the category of mistake that produced it.

Canonical, native and liquidity bridges are not comparable

A rollup's canonical bridge inherits the security of the chain itself and is slow by design. A message-passing bridge depends on an external validator set. A liquidity network never moves assets across chains at all — it pays you out of a local pool. These are different risk products and we say which one you are using in every review.

Our standing advice

Bridge only what you need, when you need it, and do not treat a bridged position as long-term storage. Where a canonical bridge exists for the route you need and you are not in a hurry, it is almost always the lower-risk choice.

FAQ

Why are bridges attacked so often?
Because they concentrate large balances behind a small number of keys or a single verification routine, and because the code has to be correct across two chains at once. It is the highest value-to-complexity ratio in crypto.
Is a fast bridge less safe?
Not inherently. Intent-based bridges are fast because a relayer fronts you funds and takes the settlement risk themselves. That can be safer for you than a validator-set bridge, and the relayer is compensated for it.
What should I check before bridging a large amount?
Whether a canonical route exists, how long the bridge has operated at the size you are sending, and whether the receiving asset is the native one or a wrapper you will need to unwind later.