Summary: Mayan is a cross-chain routing product, not a canonical bridge trust anchor. The official materials do show a real auction and solver layer, but the sharper read is simpler: Mayan mainly packages Swift fills, Circle CCTP transfers, and Wormhole-based paths behind one fast-swap surface. The control surface is route selection, driver participation, fallback logic, and quote packaging, not some novel settlement primitive of its own.
What it does:
Provides a consumer app and developer tooling for swapping or bridging assets across Solana and multiple EVM networks
Supports three documented transfer methods: Swift for intent-style fast fills, MCTP for Circle CCTP-based stablecoin transfers, and Wormhole Swap for selected asset routes built on Wormhole primitives
Runs an onchain auction model in which drivers compete to offer users the best quoted execution rate for cross-chain transfers
Exposes SDK, widget, quote and explorer APIs, referral tooling, gas-on-destination support, and explorer surfaces for integrators
Publishes security and audit materials covering core contracts and route variants such as MCTP and Swift
Key claims:
Official docs present Mayan as an execution and routing layer with large reported volume and wallet counts, which is why this note belongs with cross-chain packaging and route policy rather than with bridge-verification anchors.
Swift is the most important mechanism to understand. The docs describe an intent-style flow where drivers bid in an onchain auction and the winner fulfills on the destination chain using pre-positioned inventory.
The auction docs matter because they make clear that Mayan is not just static API routing. Solver participation, quote competition, and auction design are real parts of the product surface.
MCTP and Wormhole Swap also make the note more useful analytically: Mayan is often a wrapper around deeper rails rather than the rail users should treat as the final trust model.
Security claims about trustless contracts do not remove the practical routing question. Users still inherit Mayan’s choices about which path gets exposed, when Swift is preferred over MCTP or Wormhole routes, and how refund or fallback behavior is handled.
Whitepaper: No classic whitepaper or litepaper was found during this pass. The strongest primary materials were Mayan’s documentation set, architecture pages, audits page, and public GitHub organization; see ../whitepapers/mayan-primary-sources-2026-04-25.md.