> For the complete documentation index, see [llms.txt](https://defi-handbook.gitbook.io/defi-handbook-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://defi-handbook.gitbook.io/defi-handbook-docs/mayan-bridge-explained-routes-costs-and-settlement.md).

# Mayan Bridge Explained: Routes, Costs, and Settlement

Mayan bridge moves crypto to a supported destination chain, with an optional token swap, when a live route covers your asset pair and amount. For a [Mayan bridge](https://mayanbridge.org) transfer, select both assets and chains, check the output floor and costs, then sign. A Mayan Finance bridge transfer delivers the selected token to your destination wallet.

### What does the transfer actually deliver?

It delivers the token specified in your quote on the destination chain, rather than requiring you to bridge first and swap afterward. You can request the same asset on both sides, such as USDC on Ethereum to USDC on Solana, or a different output token. The available route depends on the exact token contracts, chains and amount; a token symbol alone does not identify the asset.

The useful distinction is between *expected output* and *minimum output*. Expected output is the quoted return; minimum output is the floor the order may settle at. Some eligible same-asset Swift transfers instead offer a fixed output, but a cross-asset swap should be treated as variable unless its quote explicitly says otherwise.

### How does a Mayan bridge move assets between chains?

The mechanism depends on the route attached to the quote. On Swift, your source transaction locks an asset on the source chain, sometimes after converting your input to a commonly held asset such as USDC or ETH. Drivers bid on the order through Solana; the winning driver pays your requested output from its own liquidity on the destination chain, then claims the locked funds after the cross-chain settlement message is verified.

That ordering explains Swift’s speed: you receive the driver’s funds before the driver is reimbursed. Wormhole’s specification describes the signed cross-chain message, called a VAA, that supports verification; its Guardian quorum is 13 of 19 signatures. Fast delivery still depends on a driver filling the order and a destination transaction succeeding, so a quoted time is an estimate.

Other routes move value differently. MCTP converts the source asset to USDC, transfers native USDC using Circle’s CCTP burn, attestation and mint process, then swaps on the destination if your requested output is another token. Wormhole Swap uses Wormhole Token Bridge transfers and a Solana auction before output is delivered. The route label tells you which settlement path, fees and failure behavior apply.

### Which route should you choose?

Choose from the routes returned for your exact pair, using the destination amount, estimated time and settlement method together. Mayan’s quote can show a quickest route and a best-return route; they may be the same. A route that looks cheap by protocol fee can still deliver less after spreads, relayer costs and source-chain gas.

* **Swift:** Driver-funded destination delivery, often the speed choice. Single transfers can reach around $1 million, depending on the chain and available liquidity.
* **MCTP:** A native-USDC transfer path through Circle CCTP, useful for larger amounts or when the recipient needs USDC. The stated capacity is around $10 million per transfer, subject to route availability.
* **Fast MCTP:** The faster CCTP variant where supported; check its quoted output against Swift rather than assuming the shortest estimated time is cheapest.
* **Wormhole Swap:** A Token Bridge path for assets such as SOL or ETH. It can suit a pair where its quoted return outweighs its longer transfer path and relayer costs.

The deciding criterion for a payment is the *amount the recipient must receive*. Mayan’s Guaranteed Price field, **swiftAuctionMode 3**, marks an eligible exact-output Swift quote; mode 2 has an expected amount and a minimum. Eligibility can change between quotes, so inspect the current quote rather than assuming that every transfer of a given token has a fixed output.

### What will it cost and how long will it take?

The total cost is visible in the output you give up plus any source-chain gas you pay separately. Check the quoted protocol fee, relayer fee, price impact, optional destination gas drop and any app referrer fee. As typical protocol rates, Swift is 0 basis points, MCTP is 0 for USDC output or around 3 for other output, Fast MCTP is around 3, and Wormhole Swap is around 10; the live quote controls.

Speed also varies by route and chain conditions. Swift can fill in as little as about 2 seconds, Fast MCTP in as little as about 5 seconds, while Wormhole Swap is generally measured in tens of seconds. Source confirmation, attestation, relaying, driver liquidity and destination congestion can extend those times. If arrival time is critical, compare the quote’s estimated settlement time with its deadline.

Slippage tolerance is a price condition, not an extra fee. For example, if a Mayan crypto bridge quote expects 1.20 SOL and applies a 50-basis-point tolerance, the output floor would be roughly 1.194 SOL; use the displayed minimum as the authoritative number. A wider tolerance raises the chance of execution at a worse price, while a tight floor can leave the order unfilled.

### How do you make the transfer?

Start with the source chain, exact input token and amount, then set the destination chain, exact output token and receiving address. For example, if you hold 250 USDC on Ethereum and need SOL in a Solana wallet, enter that pair and compare the returned routes. Verify the Solana address carefully and check whether the quote includes a destination gas drop if the wallet has no SOL for its next transaction.

Before signing, confirm the output token’s contract or mint, expected and minimum amounts, fees, route type and destination address. If you bridge tokens with Mayan from an EVM wallet using an ERC-20 input, a first transfer may also require a token allowance approval; an EIP-2612 permit can replace that approval where the token supports it. Keep enough native gas on the source chain unless the selected quote explicitly supports gasless execution.

Submit the source transaction and keep its hash. A supported gasless route instead takes a signed message and gives you an order hash, which serves the same tracking purpose. Follow the order through completion and verify the received token balance on the destination chain before using it in an app.

### What happens if the order does not fill?

An unfilled order becomes refundable after the deadline carried in its quote; it cannot settle below the signed minimum. Check the order status before retrying, so a delayed fill does not turn into an unintended second transfer. The refund may take additional onchain processing and can involve a refund relayer fee.

Swift has one easily missed refund edge case: if your input was swapped into its locked source asset before the order opened, that converted asset is what comes back. A transfer begun with one token could therefore refund as USDC or ETH on the source chain. Check the route and refund details before signing when receiving the original token back matters to your next step.