Enso vs. Across
Rift Research
Last updated
TLDR: Enso is a DeFi action and shortcut layer. Across is an intent-based interoperability protocol. Consider Enso when you need multi-step DeFi intents, not only a simple swap. 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
Enso. Enso is a unified DeFi API. The Route API finds a path into a destination token, LP or vault. The Bundle API composes ordered actions (swap, lend, borrow, deposit) into one transaction. Enso constructs transaction data for the integrating product to present for signing. The signing flow and underlying protocols determine permissions and custody assumptions. Official docs: Enso Docs. App: enso.finance.
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 | Enso | Across |
|---|---|---|
| Role | DeFi action and shortcut layer | Intent-based interoperability protocol |
| Fee | Depends on the composed route and underlying protocols | Market-quoted relayer spread and LP fee; no separate flat protocol toll |
| Coverage | Multi-chain DeFi primitives connected through Enso integrations | Supported mainnet networks, with availability determined by the exact token pair and route |
| Settlement | Atomic bundled transaction when using Bundle; otherwise the returned route tx | Canonical assets delivered by bonded relayers |
| Trust model | Enso router / wallet adapters plus each underlying protocol | Relayer-funded fills and the settlement and dispute mechanisms of the deployed Across contracts |
| Good fit for | Multi-step DeFi intents, not only a simple swap | Canonical USDC and ETH transfers between supported chains |
| Docs | Enso Docs | Across Docs |
Where each fits
Enso may fit when:
- The job is swap-plus-deposit, zap, or another multi-step action
- You want Enso to build the calldata while you keep the wallet UX
- A single-hop bridge or AMM swap is not enough
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
Enso 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 Enso when you need multi-step DeFi intents, not only a simple swap.
- 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, Enso or Across?
Neither has a universal price advantage. Enso: Depends on the composed route and underlying protocols. 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 Enso 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 Enso and Across docs?
Enso: Enso Docs. Across: Across Docs. Live rate comparison: rates.gg.
Official sources
- Enso docs: Enso Docs
- Enso app: enso.finance
- Enso — Developer home: docs.enso.build/home
- Enso — Use cases: docs.enso.build/pages/use-cases
- Enso — API: api.enso.finance/api
- 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 Enso 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.