> For the complete documentation index, see [llms.txt](https://crosschain-docs.gitbook.io/crosschain-docs-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://crosschain-docs.gitbook.io/crosschain-docs-docs/mayan-bridge-explained-choosing-a-cross-chain-route.md).

# Mayan Bridge Explained: Choosing a Cross-Chain Route

Mayan Bridge can deliver a destination-chain asset in one flow when a live route supports the exact pair and its net output justifies the wait and execution risk. For a frequent user, the choice comes down to delivered units, total fees, settlement time, and what happens if the transfer cannot complete.

### Mayan Bridge as a One-Flow Cross-Chain Swap

A Mayan cross-chain swap combines asset transfer and conversion so you receive the token you intend to use on the destination chain. It fits when you would otherwise bridge an intermediate asset and make a second trade. A chain being supported does not establish that your token, transfer direction, or size has a usable route; thin liquidity can erase the benefit of fewer steps.

Suppose you hold BTC on Bitcoin and want SOL on Solana. Check that the exact pair and amount are available before sending funds. The [Mayan Bridge service](https://mayanbridge.org) moves and swaps assets across chains in one flow, so it is the route to evaluate when you want the destination asset without arranging a separate trade there. Verify the recipient address and keep enough BTC to pay the source transaction fee.

Compare output at a common reference price, including costs outside the quoted conversion. Say $2,000 of BTC produces SOL worth $1,970 and the Bitcoin transaction costs $8: the all-in shortfall is $38, or 1.9%. Compare a Mayan Bridge route with alternatives at roughly the same time; a stale quote and a fresh quote do not measure the same market. Account for any bridge or solver fee, destination swap price impact, and destination gas where those are charged separately.

One flow is not one atomic transaction. The source transfer must reach a route’s confirmation threshold; a message or liquidity provider then enables delivery, and a destination trade may complete the conversion. The Bitcoin Developer Guide puts the average interval between blocks at about ten minutes, so a route requiring, say, two confirmations has a nominal twenty-minute block wait with substantial variance. If its quote expires during that wait, check whether the route fixes the output, reprices it, or refunds the deposit, including which asset and chain receive the refund.

Before committing, check four route-specific facts:

* The destination token’s mint or contract address, rather than its ticker alone.
* The minimum received after price impact and any configurable slippage tolerance.
* The source confirmation requirement and estimated time to destination delivery.
* The claim or refund path if destination execution fails.

To bridge, set the source asset, destination asset, amount, and recipient; review those facts against the live route, then authorize the source transfer. A native BTC send has no token allowance, while a contract-based token route may require approval before transfer. Track the source transaction and confirm the final token balance on the destination chain before treating the job as complete.

### Bridge First, Then Swap on the Destination Chain

A separate bridge followed by a destination swap gives you control over each leg and may deliver more when the combined markets are deeper. It fits repeat transfers where you already hold destination gas and can reuse a familiar bridge route. It is less convenient when the destination trade must happen immediately or when an extra approval and transaction outweigh a small price improvement.

Start by checking what the bridge actually delivers. A bridged token may have several wrapped versions with the same ticker, and the deepest SOL market may pair against only one of them. Price the bridge output against the destination pool you can use, then subtract source gas, bridge charges, destination gas, swap fee, and price impact. If the bridge delivers $1,980 of usable value but the destination trade costs $18, it loses to a one-flow output worth $1,970 only if the one-flow source costs add more than the remaining $8 difference.

This route also splits execution risk. The bridge can complete while the destination swap fails or becomes expensive, leaving you with the intermediate token. Set a sensible minimum received for the swap; a 0.5% tolerance on $2,000 allows roughly $10 of adverse execution beyond the quoted amount. A Mayan cross-chain swap is the simpler choice when that exposure and the extra transaction cost more than the manual route saves.

### Canonical Bridge for an Asset That Should Stay the Same

A canonical bridge is the direct choice when you need an asset’s official representation across a base chain and its associated layer 2, with no asset conversion. It is a poor fit for BTC on Bitcoin to SOL on Solana, or whenever the destination token must be acquired through a swap. Confirm the canonical token mapping by contract address: a familiar ticker does not prove that two representations have the same redemption path.

Direction decides the timing. A deposit into a layer 2 and a withdrawal back to its base chain can have very different settlement rules; Ethereum.org describes a roughly seven-day challenge period for a typical optimistic-rollup canonical withdrawal. A liquidity-funded route can pay sooner by taking over the pending withdrawal, but that speed has a price and depends on available liquidity. Compare the value of earlier access with its fee rather than treating the two arrival times as equivalent.

Canonical transfers can also require a later proof or finalization transaction, so count that action and its gas in the total. Check whether the destination wallet will have enough native gas to use the received token. This option wins when preserving the canonical asset and its withdrawal path matters more than immediate conversion or the fewest actions.

### Exchange Deposit and Withdrawal Across Networks

An exchange-mediated transfer can be efficient when you already keep funds there and it supports both the deposit network and the withdrawal asset you need. The sequence is deposit, any necessary trade, then withdrawal on the selected network. It does not fit a self-custody workflow that requires a predictable completion time or a transaction you can execute entirely on-chain.

Check the deposit asset and network separately from the withdrawal asset and network. A matching ticker is insufficient: sending a token to an address on the wrong network can make recovery impossible, and some deposits require a memo or tag. Include trading spread, deposit confirmation time, withdrawal charges, and any size limits in the comparison. Exchange credit, trading availability, and withdrawal availability are separate stages, so an on-chain confirmation does not guarantee immediate delivery.

I would price the one-flow route first for an asset conversion, then compare its delivered units and arrival window with a bridge plus swap. I would use a canonical bridge when I need the canonical asset, and an exchange route only when its custody and timing already fit the transfer.