Set topology
2 rails live in a canonical or venue-heavy model; the rest depend more on liquidity, messaging or intents.
Bridge Compare separates real multichain base from bridge narrative.
This route stays deliberately public and maintainable. It compares bridges on TVL, reach and protocol base because several flow endpoints no longer stay openly usable.
💡
Method note
Bridge Compare uses public DefiLlama data plus a curated bridge canon. That keeps wrapped assets out of the board and leaves only rails that matter for transport risk.
Bridges
6
structural canon
Bridge TVL
$12.7B
operating sample
Average reach
7.8
chains per rail
Positive 7d
4
rails expanding
Structural lenses
Start with transport model, operator control and reach quality before using TVL as a comfort signal.
Operational control
2 names still carry high operator control. That risk does not disappear just because TVL is larger.
Useful reach
4 rails cover five or more chains, but reach quality depends on settlement and messaging, not just a chain counter.
Operating profiles
Operating profiles
These cards compress the useful read: what the bridge is, how concentrated the path stays and what deserves slower review.
needs more context
Coinbase Bridge
canonical route / high control / Multi-Chain
The real risk is not only smart contracts; custody, freeze posture and operator dependence matter too.
needs slower review
Hyperliquid Bridge
venue bridge / high control / Multi-Chain
It should be read as platform and exit risk, not as comfort driven by aggregated TVL.
needs more context
Portal
liquidity bridge / medium control / Multi-Chain
Wide reach does not mean lower risk when the route depends on more liquidity, routes and finality assumptions.
needs more context
Stargate
liquidity bridge / medium control / Multi-Chain
Risk concentrates in pools, messaging and configuration changes, not only in TVL.
cleaner defensive gate
Across
intent bridge / medium control / Ethereum
The defensive read runs through relayers, backstop and fast-route composition, not APY or marketing.
needs more context
deBridge
intent bridge / medium control / Multi-Chain
Its upside is flexibility; the tradeoff is reviewing validators, messaging and real route coverage.
Bridge comparison
Source: DefiLlama + curated bridge universe
Bridge comparison
| Bridge | Model | TVL | Reach | 7d | Risk gate |
|---|---|---|---|---|---|
| Coinbase Bridge | canonical route | $5.7B | 5 | +4.0% | 64/100 / needs more context |
| Hyperliquid Bridge | venue bridge | $4.6B | 2 | -3.7% | 58/100 / needs slower review |
| Portal | liquidity bridge | $1.9B | 24 | +14.9% | 61/100 / needs more context |
| Stargate | liquidity bridge | $480M | 4 | +2.4% | 60/100 / needs more context |
| Across | intent bridge | $35M | 6 | +9.1% | 69/100 / cleaner defensive gate |
| deBridge | intent bridge | $11M | 6 | -5.3% | 63/100 / needs more context |
Curated comparison
The comparison leaves out wrappers and names that distort the bridge category. This board keeps rails that actually matter for moving capital across domains.
What it solves
It separates canonical routes, intent bridges and liquidity rails before the reader mistakes reach for safety.
Risk gate
Read bridges through Risk Lab
Bridge risk stays closer to messaging and operational exposure than to plain TVL comfort.
Open Risk Lab ->Protocol layer
Protocol Compass
Use the protocol route when you need category context before comparing bridge-specific footprints.
Open Protocol Compass ->Governance
Execution context
Some bridge risk still sits in governance and upgrade control, not only in the bridge architecture itself.
Open governance ->