Search
Search projects, tokens and protocols by name or address
Liquid stakingSoon
And more
Pinned
Recently viewed
Pin a project to keep it here. Saved only in this browser.
Intent bridges
This dashboard provides an overview of intent-based bridge protocols. It combines indexed transfer activity with curated intent-specific properties such as user recovery paths, solver access, settlement model, active tokens and active chain routes.
26/26Chains
+21
Total volume
Last 24 hours
Total transfers
Last 24 hours
Intent Bridge Dominance by Volume
Last 24 hours
Total volume
Last 24 hours
Total transfers
Last 24 hours
Top Tokens by Volume
Last 24 hours
Transfer speed
Select two chains to compare intent bridge transfer speed.
All intent bridges
Transfer size distribution
Last 24 hours
Intent Bridge Comparison
Last 24 hours
Activity metrics come from indexed transfers. Intent mechanics are curated protocol properties.
Top
path | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Top
path | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Top
path | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1 |  | Across | $24.52 M | 6s | $850.71 | 18 | 9 | | If no relayer fast-fills a deposit, Across can complete it through the protocol slow-fill path. This is not available for chains without an Ethereum canonical bridge adapter, nor for V5 Gateway deposits, which are instead refunded on the origin chain after the fill deadline expires. | Relayers compete to fill deposits and receive repayment. | Relayers compete to fill cross-chain transfer intents across supported chains and assets. | Relayer repayment is settled through the Across system and can be escalated to token voting via UMA. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
2 |  | Stargate | $17.60 M | Bus: N/A Taxi:1m 16s | $30.94 K | 12 | 4 |  | Source-side checks revert before funds move; destination delivery depends on the DVN signature. There is no source-chain refund path after funds move. | Execution is permissionless via LayerZero and Stargate liquidity pools, but requires DVN liveness. | Transfers use Stargate liquidity and omnichain routing. | Stargate uses LayerZero-based cross-chain messaging. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
3 |  | deBridge DLN | $15.84 M | 5m 20s | $7.60 K | 13 | 124 |  | Unfilled orders can be cancelled through the DLN flow. | Order fulfillment is designed around independent takers. | Users create orders that takers can fulfill. | Order state and settlement use deBridge infrastructure. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
4 |  | Mayan | $9.97 M | 14s | $1.09 K | 10 | 356 | | There is no onchain refund option. Unfulfilled Swift orders can be refunded from the source contract with a Wormhole or refund-verifier message. | Drivers compete in Mayan auctions. | Solvers compete to fill cross-chain swap intents. | Mayan uses Wormhole messages to prove destination fulfillment or refunds and unlock source-chain funds. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
5 |  | LI.FI | $6.76 M | 10s | $2.10 K | 16 | 6 |  | Escrow orders can be refunded after expiry; Compact orders expire without moving locked funds unless fills are proven in time. | Whitelisted solvers have access to an internal API and marketplace, but solving is generally permissionless in OIF. | Uses the Open Intents Framework standard. | Solvers fill destination outputs, then claim source inputs after oracle proofs of the fills. Oracles are configurable by LI.FI. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
6 |  | Relay | $4.11 M | 5s | $673.73 | 26 | 226 | | There is no onchain refund option. Failed transfers depend on Relay-operated recovery. | Transfers are filled by Relay-operated infrastructure. | Users pay against a quote from the centralized Relay API and Relay solvers fill on the destination chain from their own liquidity. | Settlement depends on Relay's centralized oracle and allocator flow: escrowed deposits are released by a single allocator signature, and the escrow owner can replace the allocator without delay. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
7 |  | 1inch Fusion+ | $2.17 M | 1m 7s | $6.74 K | 11 | 29 | | The filling resolver, or later a RES holder, must cancel the source-chain escrow to return the deposit to the user. | Orders use timed resolver whitelists, followed by access for owner-issued RES NFT holders. | A resolver fills a user order through matching source- and destination-chain escrows. | Matching escrows use one secret and separate source- and destination-chain timelocks. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
8 |  | Celer cBridge | $365.28 K | 9m 31s | $1.41 K | 9 | 6 | | There is no onchain refund option. Failed pool transfers can be withdrawn on the source chain using gateway data signed by the Celer SGN. | Solvers provide the signatures of the offchain Celer signer quorum with their transaction. | Transfers are filled from the liquidity pool. | Relay and refund messages must be authorized by a Celer signer quorum. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
9 |  | Meson | $309.55 K | 6m 21s | $2.24 K | 8 | 3 |  | There is no onchain refund option. The central liquidity pool implementation source code is unavailable. | Execution depends on Meson LPs locking destination-chain liquidity in the smart contract escrow. Execution is permissionless but needs offchain signatures by the centralized oracle. | Transfers are filled from a central liquidity pool on each chain. | Settled through Meson bridge contracts. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
10 |  | Gas.zip | $328.49 | 6s | $1.27 | 11 | 5 | | There is no onchain refund option. Invalid deposits are handled through Gas.zip support. | No open solver marketplace is exposed. | Focused on sending small gas balances across chains. | Settlement depends on Gas.zip internal, centralized accounting. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
11 |  | Butter Network | — | — | — | — | — | — | — | There is no onchain refund: once assets are locked on the source chain, no contract path returns them. Failed destination deliveries can be permissionlessly re-executed via retryMessageIn, and failed token payouts are swept to an admin-set failedReceiver address. | There are no independent solvers or auctions: destination payouts come from bridge-held pool liquidity and only after settlement on the MAP relay chain. Anyone can trigger a payout by relaying the settled message with a receipt proof. | Transfers are filled from bridge-owned liquidity on the destination chain after the message settles on the MAP relay chain. MAPO is the only token that is burned and minted instead. | Transfers settle through the MAP relay chain, an external proof-of-stake chain. Destination chains verify only BLS signatures of its validator set via onchain light clients. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||