Across vs. Mayan
Rift Research
Last updated
TLDR: Across is an intent-based interoperability protocol. Mayan is a fast cross-chain swap protocol. Consider Across when you are moving canonical USDC or ETH between major chains and care about speed. Consider Mayan when you need a fast EVM ↔︎ Solana or similar corridor. 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.
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 | Across | Mayan |
|---|---|---|
| Role | Intent-based interoperability protocol | Fast cross-chain swap protocol |
| Fee | Market-quoted relayer spread and LP fee; no separate flat protocol toll | Priced into the auction / route quote |
| Coverage | Supported mainnet networks, with availability determined by the exact token pair and route | Solana, Ethereum, Base, Arbitrum, Optimism, BNB Chain, Sui, HyperEVM, Monad and others listed in Mayan docs |
| Settlement | Canonical assets delivered by bonded relayers | Native on the destination; path depends on Swift, MCTP or Wormhole |
| Trust model | Relayer-funded fills and the settlement and dispute mechanisms of the deployed Across contracts | Intent auction plus the messaging layer used on that path (CCTP or Wormhole) |
| Good fit for | Canonical USDC and ETH transfers between supported chains | Fast EVM ↔︎ Solana and related corridors |
| Docs | Across Docs | Mayan 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
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
Across 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 Across when you are moving canonical USDC or ETH between major chains and care about speed.
- 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, Across or Mayan?
Neither has a universal price advantage. Across: Market-quoted relayer spread and LP fee; no separate flat protocol toll. 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 Across 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 Across and Mayan docs?
Across: Across Docs. Mayan: Mayan 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
- 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 Across 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.