Enso vs. Mayan
Rift Research
Last updated
TLDR: Enso is a DeFi action and shortcut layer. Mayan is a fast cross-chain swap protocol. Consider Enso when you need multi-step DeFi intents, not only a simple swap. Consider Mayan when you need a fast EVM ↔︎ Solana or similar corridor. 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.
Mayan. Mayan routes cross-chain swaps through Swift (intent auction), MCTP (Circle CCTP plus Mayan auction), and Wormhole Swap. It is widely used on EVM ↔︎ Solana and similar corridors. Official docs: Mayan Docs. App: mayan.finance.
Short version
| Dimension | Enso | Mayan |
|---|---|---|
| Role | DeFi action and shortcut layer | Fast cross-chain swap protocol |
| Fee | Depends on the composed route and underlying protocols | Priced into the auction / route quote |
| Coverage | Multi-chain DeFi primitives connected through Enso integrations | Solana, Ethereum, Base, Arbitrum, Optimism, BNB Chain, Sui, HyperEVM, Monad and others listed in Mayan docs |
| Settlement | Atomic bundled transaction when using Bundle; otherwise the returned route tx | Native on the destination; path depends on Swift, MCTP or Wormhole |
| Trust model | Enso router / wallet adapters plus each underlying protocol | Intent auction plus the messaging layer used on that path (CCTP or Wormhole) |
| Good fit for | Multi-step DeFi intents, not only a simple swap | Fast EVM ↔︎ Solana and related corridors |
| Docs | Enso Docs | Mayan 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
Mayan may fit when:
- Solana is on one side of the route
- You want an intent fill rather than an AMM curve
- MCTP can reuse CCTP for a USDC leg
Key differences
Enso and Mayan 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 Mayan when you need a fast EVM ↔︎ Solana or similar corridor.
- 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 Mayan?
Neither has a universal price advantage. Enso: Depends on the composed route and underlying protocols. Mayan: Priced into the auction / route quote. 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 Mayan?
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 Mayan docs?
Enso: Enso Docs. Mayan: Mayan 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
- Mayan docs: Mayan Docs
- Mayan app: mayan.finance
- Mayan — What is Mayan?: docs.mayan.finance/
- Mayan — Swift v2: docs.mayan.finance/architecture/swift-v2
- Mayan — MCTP (CCTP path): docs.mayan.finance/architecture/mctp
- Mayan — Quote API: docs.mayan.finance/integration/quote-api
Get the Best of Both With Rift
Rift is a strong alternative to choosing between Enso and Mayan. 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.