Mayan Swift on RAVN: Cross-Chain Intent Auction
Mayan Swift is RAVN's intent-auction rail for cross-chain and cross-ecosystem swaps. Driver liquidity on the destination; you sign the origin transaction when Mayan wins.
Quick answer
Mayan Swift is the Mayan product path RAVN integrates (not Mayan's Wormhole wrap product). Solvers auction fills and deliver the destination asset. When Mayan wins a RAVN race, execution is a TRANSACTION built from Mayan's payload for EVM or Solana origins.
Where Mayan races
- EVM xEVM cross-chain with Across, Relay, NEAR Intents.
- X-ecoEVM and Solana with Across, Relay, NEAR Intents.
- SOLSolana same-chain race with Jupiter Ultra, Relay, NEAR Intents.
Only chains Mayan maps are quoted. zkSync and World Chain style gaps simply omit Mayan from that pair.
Swift, not wrap theater
RAVN uses Mayan Swift specifically for canonical-style delivery through driver liquidity already on the destination chain. Product language is no RAVN bridge and no RAVN-minted synthetic. You still depend on Mayan's settlement security model, which is independent venue risk.
Execution sketch
- EVM origin: transaction payload (and approvals when needed) from Mayan's Swift from-EVM flow.
- Solana origin: versioned transaction built from Mayan instructions and lookup tables.
- Always branch on RAVN
executionType, not raw Mayan SDK types, as an integrator.
Try it in the app
Live in beta. Parallel venues, best execution, canonical assets. RAVN never holds your funds.
FAQ
Is this Mayan Wormhole bridging?
RAVN integrates Mayan Swift for the auction and driver-liquidity path, not as a wrap marketing story. Canonical destination selection still matters in the app.
Does Mayan do native BTC?
Native BTC on RAVN is Garden, Relay, and NEAR Intents. Mayan is for the EVM and Solana races listed above.
What do I sign?
A TRANSACTION when Mayan wins. EVM or Solana payload depending on origin.
Why race Mayan with Across?
Different solvers, inventory, and latency. Parallel quotes protect users from single-venue pricing.
