Across vs. 1inch
Rift Research
Last updated
TLDR: Across is an intent-based interoperability protocol. 1inch is a DEX aggregator and execution stack. Consider Across when you are moving canonical USDC or ETH between major chains and care about speed. Consider 1inch when you want onchain liquidity aggregation across supported sources. 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.
1inch. 1inch is a long-running DEX aggregator. Pathfinder splits routes across on-chain liquidity. Fusion and Fusion+ add intent-style and cross-chain execution. The business portal exposes swap, orderbook and fusion APIs. Official docs: 1inch Portal Docs. App: app.1inch.io.
Short version
| Dimension | Across | 1inch |
|---|---|---|
| Role | Intent-based interoperability protocol | DEX aggregator and execution stack |
| Fee | Market-quoted relayer spread and LP fee; no separate flat protocol toll | Path-dependent: underlying pools plus any interface or Fusion components |
| Coverage | Supported mainnet networks, with availability determined by the exact token pair and route | Major EVM chains plus Solana on current 1inch portal docs |
| Settlement | Canonical assets delivered by bonded relayers | On-chain via the 1inch router, or Fusion resolvers |
| Trust model | Relayer-funded fills and the settlement and dispute mechanisms of the deployed Across contracts | 1inch router and limit-order contracts plus underlying pools |
| Good fit for | Canonical USDC and ETH transfers between supported chains | Onchain liquidity aggregation across supported sources |
| Docs | Across Docs | 1inch Portal 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
1inch may fit when:
- The supported same-chain or cross-chain product fits your route
- Split routing across DEXs reduces impact on a large ticket
- You already integrate 1inch Fusion or the Pathfinder API
Key differences
Across and 1inch 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 1inch when you want onchain liquidity aggregation across supported sources.
- 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 1inch?
Neither has a universal price advantage. Across: Market-quoted relayer spread and LP fee; no separate flat protocol toll. 1inch: Path-dependent: underlying pools plus any interface or Fusion components. 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 1inch?
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 1inch docs?
Across: Across Docs. 1inch: 1inch Portal 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
- 1inch docs: 1inch Portal Docs
- 1inch app: app.1inch.io
- 1inch — Developer portal: portal.1inch.dev/documentation
- 1inch — 1inch app: app.1inch.io
Get the Best of Both With Rift
Rift is a strong alternative to choosing a single provider. Its rate comparison includes Across and 1inch alongside additional venues, while the Rift API routes orders across its supported execution integrations. You can compare both approaches and get one execution flow for the available route.
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.