LI.FI vs. Across
Rift Research
Last updated
TLDR: LI.FI is a cross-chain routing and aggregation layer. Across is an intent-based interoperability protocol. Consider LI.FI when you need broad coverage with an SDK, widget and agent tools. Consider Across when you are moving canonical USDC or ETH between major chains and care about speed. Confirm the live winner on rates.gg.
What each protocol is
LI.FI. LI.FI is a routing and orchestration layer. One integration reaches bridges, DEXs, solvers and yield protocols for same-chain swaps, cross-chain swaps, and multi-step flows. Official docs: LI.FI Docs. App: li.fi.
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.
Short version
| Dimension | LI.FI | Across |
|---|---|---|
| Role | Cross-chain routing and aggregation layer | Intent-based interoperability protocol |
| Fee | Integrator and service fees configured per integration; see LI.FI docs | Market-quoted relayer spread and LP fee; no separate flat protocol toll |
| Coverage | Supported networks through bridges, DEXs and solvers; coverage varies by route | Supported mainnet networks, with availability determined by the exact token pair and route |
| Settlement | Depends on the winning underlying route (can be wrapped or native) | Canonical assets delivered by bonded relayers |
| Trust model | LI.FI router plus each underlying bridge, DEX or solver | Relayer-funded fills and the settlement and dispute mechanisms of the deployed Across contracts |
| Good fit for | Broad coverage with an SDK, widget and agent tools | Canonical USDC and ETH transfers between supported chains |
| Docs | LI.FI Docs | Across Docs |
Where each fits
LI.FI may fit when:
- You need one integration that covers the long tail of chains and tokens
- You want widgets, SDK, MCP and agent tooling in the same stack
- The product is a general-purpose cross-chain app, not a single corridor
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
Key differences
LI.FI and Across 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 LI.FI when you need broad coverage with an SDK, widget and agent tools.
- Use Across when you are moving canonical USDC or ETH between major chains and care about speed.
- 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, LI.FI or Across?
Neither has a universal price advantage. LI.FI: Integrator and service fees configured per integration; see LI.FI docs. Across: Market-quoted relayer spread and LP fee; no separate flat protocol toll. 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 LI.FI a substitute for Across?
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 LI.FI and Across docs?
LI.FI: LI.FI Docs. Across: Across Docs. Live rate comparison: rates.gg.
Official sources
- LI.FI docs: LI.FI Docs
- LI.FI app: li.fi
- LI.FI — What LI.FI provides: docs.li.fi/introduction/introduction
- LI.FI — Product stack: docs.li.fi/introduction/product-stack
- LI.FI — API overview: docs.li.fi/api-reference/introduction
- 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
Get the Best of Both With Rift
Rift is a strong alternative to choosing between LI.FI and Across. 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.