If your Mayan bridge transfer starts on a chain with expensive gas, compare the amount you will receive with every source transaction you must pay for. A gasless Swift route can remove the need to hold native gas when available. Otherwise, avoiding a separate token approval or source swap may save more than choosing the route with the lowest stated protocol fee.
What happens during a cross-chain transfer?
A cross-chain transfer starts with an order on the source chain and ends when the requested token reaches the destination wallet. When you start a Mayan bridge transfer, the source transaction may convert your input into a token the route can settle, then lock or send it. The Mayan Finance bridge quote describes the output you want; the route determines how it gets there.
On Swift, a driver—a party that fills the order—pays the destination wallet from funds it already holds there. Drivers compete to offer the output amount, and the winning driver later claims the locked source funds. That is why the recipient can receive a token before a conventional bridge transfer has finished moving value between chains.
MCTP takes a different path: it converts the input to native USDC if needed, moves that USDC through Circle CCTP, and can swap it into the requested token on arrival. Fast MCTP uses a faster CCTP settlement path. Wormhole Swap transfers through Wormhole’s Token Bridge and uses a swap auction; depending on the asset and route, a token bridge can deliver a wrapped representation rather than the destination chain’s native version.
Which routes can reduce source gas?
For a Mayan bridge order from an eligible EVM wallet, a gasless Swift quote is the first route to check when the wallet holds the input token but little or no native gas. You sign an order, and a relayer submits the source transaction. Gasless describes what the wallet pays directly; the driver’s and relayer’s costs still affect the quoted output.
A regular Swift order requires the wallet to submit a source transaction, but it may still be economical if it avoids an extra swap and has a strong output quote. If an ERC-20 token has no usable allowance, approval may require a separate paid transaction before the order. A supported permit can replace that approval transaction with a signature, so check the wallet’s actual confirmation steps rather than assuming every route takes one transaction.
MCTP and Fast MCTP are useful comparisons when native USDC is the input or desired output, particularly if a Swift quote is unavailable or poor for the amount. Fast settlement does not itself reduce the gas used by your source transaction. Wormhole Swap can reach assets that other paths cannot, but its source transaction and relaying costs deserve close inspection when source gas is the constraint.
What will the routes cost, and how long will they take?
Source gas is the sum of the gas used by each wallet transaction multiplied by its effective gas price. Ethereum.org explains that price as the base fee plus a priority fee; Etherscan’s gas tracker shows why a quote taken during a quiet period can be misleading later. A contract call uses more gas than a simple ETH transfer, and approval adds another transaction when required.
For an illustration, suppose approval uses 50,000 gas and the bridge call uses 200,000 gas at an effective 30 gwei. Together they cost 0.0075 ETH; at a hypothetical $2,000 per ETH, that is $15 before any difference in quoted output. If the approval is already in place, only the bridge call remains in this example: 0.006 ETH, or $12 at that price.
To bridge tokens with Mayan, compare input value minus final output value plus source gas paid separately, using the same input amount and destination token for every quote. Protocol fees alone are often small by comparison: Swift commonly shows zero, MCTP is roughly zero to 0.03% depending on the output, and Wormhole Swap is around 0.1%. The quote also reflects conversion, price impact, relayer charges and any destination gas you request, so read its live breakdown rather than adding those items twice.
As a quick what-if, say two routes each start with 1,000 USDC. A gasless route delivering 990 USDC beats a regular route delivering 997 USDC if that regular route also makes you spend the illustrative $15 in source gas: the latter leaves $982 of combined value. If you already have approval and source gas falls to $2, the same regular quote leaves $995 and becomes the better value.
Swift can arrive in seconds when a driver fills promptly, though execution and chain conditions can extend that to minutes. Fast MCTP may also complete in seconds to minutes; standard CCTP paths and Wormhole transfers can take minutes or longer because they wait for confirmations, attestations and destination execution. Treat the displayed ETA as an estimate, especially when a source transaction is still waiting to be included.
What can change the result after you sign?
The main variables are route availability, executable output and the order deadline. A Swift driver needs sufficient destination liquidity for your amount, while a CCTP path needs supported chains and the correct native USDC contract. Two assets labelled USDC can represent different tokens, so verify the token contract and destination chain before comparing quotes.
Check both the expected output and the minimum output: the latter is the floor you authorize if the rate moves. If an order cannot fill before its deadline, it becomes refundable; a refund can incur a relayer fee. One easily missed detail is that a Swift order which converted your input on the source chain may refund that converted asset, typically USDC or ETH, rather than the token you originally supplied.
How should you choose a route before confirming?
Get fresh Mayan bridge quotes for the same input amount, destination address and exact output token. Compare the route type, expected and minimum output, ETA, gasless eligibility, source transaction count and any approval your wallet requests. Then estimate source gas at the current fee rate and convert it into the same unit as the output so the totals are comparable.
If the destination wallet has no native gas token, consider a gas drop—the route delivers a small amount for later transactions—and include its effect on output. Confirm the destination address and token contract, especially when moving between EVM and non-EVM chains. After submission, track the order until the destination transfer completes or the refund is confirmed.
Choose the available route with the best acceptable minimum output after source gas and all required approvals, provided its ETA and destination token meet your needs.