Relay vs. Enso
Rift Research
Last updated
TLDR: Relay is a cross-chain intents and payments protocol. Enso is a DeFi action and shortcut layer. Consider Relay when you need fast small-to-mid transfers and payments across many networks. Consider Enso when you need multi-step DeFi intents, not only a simple swap. Confirm the live winner on rates.gg.
What each protocol is
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.
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.
Short version
| Dimension | Relay | Enso |
|---|---|---|
| Role | Cross-chain intents and payments protocol | DeFi action and shortcut layer |
| Fee | Solver spread plus small protocol components, quoted per order | Depends on the composed route and underlying protocols |
| Coverage | Networks and assets supported by the selected Relay route | Multi-chain DeFi primitives connected through Enso integrations |
| Settlement | Solver fronts destination liquidity; protocol settles after proof | Atomic bundled transaction when using Bundle; otherwise the returned route tx |
| Trust model | Non-upgradable Depository contracts; Allocator-authorised withdrawals; audited settlement stack | Enso router / wallet adapters plus each underlying protocol |
| Good fit for | Fast small-to-mid transfers and payments across many networks | Multi-step DeFi intents, not only a simple swap |
| Docs | Relay Docs | Enso Docs |
Where each fits
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
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
Key differences
Relay and Enso 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 Relay when you need fast small-to-mid transfers and payments across many networks.
- Use Enso when you need multi-step DeFi intents, not only a simple swap.
- 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, Relay or Enso?
Neither has a universal price advantage. Relay: Solver spread plus small protocol components, quoted per order. Enso: Depends on the composed route and underlying protocols. 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 Relay a substitute for Enso?
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 Relay and Enso docs?
Relay: Relay Docs. Enso: Enso Docs. Live rate comparison: rates.gg.
Official sources
- 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
- 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
Get the Best of Both With Rift
Rift is a strong alternative to choosing between Relay and Enso. 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.