Across vs. Relay
Rift Research
Last updated
TLDR: Across is an intent-based interoperability protocol. Relay is a cross-chain intents and payments protocol. Consider Across when you are moving canonical USDC or ETH between major chains and care about speed. Consider Relay when you need fast small-to-mid transfers and payments across many networks. Confirm the live winner on rates.gg.
What each protocol is
Across. Across is an intents protocol for bridging and cross-chain swaps. Relayers front destination liquidity. Across advertises approximately two-second fills on supported mainnet routes; actual timing depends on the route. Its intent settlement and refund mechanisms are separate from that initial fill. Official docs: Across Docs. App: across.to.
Relay. Relay is a cross-chain intents protocol. Users deposit into a per-chain Depository; solvers fill on the destination; a dedicated settlement chain and oracle reimburse the solver. Official docs: Relay Docs. App: relay.link.
Short version
| Dimension | Across | Relay |
|---|---|---|
| Role | Intent-based interoperability protocol | Cross-chain intents and payments protocol |
| Fee | Market-quoted relayer spread and LP fee; no separate flat protocol toll | Solver spread plus small protocol components, quoted per order |
| Coverage | Supported mainnet networks, with availability determined by the exact token pair and route | Networks and assets supported by the selected Relay route |
| Settlement | Canonical assets delivered by bonded relayers | Solver fronts destination liquidity; protocol settles after proof |
| Trust model | Relayer-funded fills and the settlement and dispute mechanisms of the deployed Across contracts | Non-upgradable Depository contracts; Allocator-authorised withdrawals; audited settlement stack |
| Good fit for | Canonical USDC and ETH transfers between supported chains | Fast small-to-mid transfers and payments across many networks |
| Docs | Across Docs | Relay Docs |
Where each fits
Across may fit when:
- You are moving USDC or ETH between major supported chains
- Fast destination fills matter; confirm the estimate for your route
- You want a dedicated intent rail rather than a meta-aggregator
Relay may fit when:
- Speed on a small or mid-size transfer matters most
- You need a long list of networks from one integration
- The job is a payment or simple transfer, not a multi-step DeFi action
Key differences
Across and Relay should be compared on the job you need to complete: the input asset, destination asset and chain, trade size, execution method and custody assumptions. They may overlap on some routes and complement each other on others. A broader chain list or faster advertised fill does not establish a better net rate. Compare executable quotes in the same window, including gas and every underlying step.
When to use which
- Use Across when you are moving canonical USDC or ETH between major chains and care about speed.
- Use Relay when you need fast small-to-mid transfers and payments across many networks.
- If both can quote the same route, take the better net output after fees, time and settlement type. Check that print on rates.gg.
FAQ
Which is cheaper, Across or Relay?
Neither has a universal price advantage. Across: Market-quoted relayer spread and LP fee; no separate flat protocol toll. Relay: Solver spread plus small protocol components, quoted per order. Compare executable quotes for the same size, destination and time window, including gas, underlying venue costs and any extra transfer. Expected output and minimum received are different figures; compare like with like.
Is Across a substitute for Relay?
Only on overlapping pairs and chains. When both can quote the same route, take the better net output after fees and time. When only one supports the asset or chain, that one is the only option.
Where are the official Across and Relay docs?
Across: Across Docs. Relay: Relay Docs. Live rate comparison: rates.gg.
Official sources
- Across docs: Across Docs
- Across app: across.to
- Across — Introduction: docs.across.to/introduction
- Across — Features and fill times: docs.across.to/introduction/features
- Across — API reference: docs.across.to/api-reference
- Relay docs: Relay Docs
- Relay app: relay.link
- Relay — How Relay works: docs.relay.link/how-relay-works
- Relay — Protocol design: docs.relay.link/references/protocol/how-it-works
- Relay — Security and audits: docs.relay.link/references/protocol/security
Get the Best of Both With Rift
Rift is a strong alternative to choosing between Across and Relay. It brings routes from both together with additional venues on supported pairs, comparing available quotes to find the best net execution for your order. You get the strengths of both through one API.
Rift adds no router fee and uses secure hardware enclaves to enforce noncustodial execution. Underlying venue fees, spreads and network costs still apply, and availability depends on the asset, chain and order size. The live quote shows the route and expected output.