Mayan Bridge turns cross-chain transfers into one transaction

Mayan Bridge lets teams send funds from one blockchain and receive a chosen token on another, combining a cross-chain transfer and conversion in one transaction. Mayan’s SDK documentation lists several route types, including Swift, an intent-based auction, and MCTP routes that use Circle’s CCTP for stablecoins.

How does Mayan Bridge move funds across chains?

A team specifies the source token, destination chain and token, recipient address, and minimum acceptable output. Mayan’s documentation says independent solvers compete to fulfil Swift orders; the selected solver delivers the destination tokens, then claims the source funds after delivery is verified through the protocol.

That order of settlement puts the interim source-chain reorganisation risk on the solver, according to Mayan. Teams evaluating mayan bridge transfers should still review each quote’s route, estimated output and minimum output: those terms determine what the recipient can expect, while the route determines how settlement works.

Which route should a team choose?

The route depends on the assets and chains involved. Mayan’s SDK identifies Swift as its primary intent-based route, MCTP and Fast MCTP as options over Circle CCTP suited to high-value stablecoin transfers, and Wormhole as a legacy Token Bridge route. Availability varies by pair, so teams need to compare the quotes returned for their transaction.

• Swift: solvers compete to fulfil an order; check the minimum output and whether the quote offers a guaranteed price.
• MCTP: uses Circle’s CCTP, so it may suit stablecoin transfers where that settlement path is available.
• Wormhole: routes through the Wormhole Token Bridge; Mayan documents a separate driver auction for execution.
• Same-chain: Mayan’s SDK also returns same-chain swap routes, which do not move funds between blockchains.

These options make a Mayan bridge transfer more than a simple asset relay: a team can specify the asset it needs at the destination, rather than bridge first and swap in a second step. That can reduce operational steps, though the quote, supported route and settlement method still matter.

What should teams check before sending funds?

Teams should confirm the destination address and token, compare the quoted output with the minimum, and account for any required source-chain approval or gas. Mayan’s SDK says ERC-20 inputs require an allowance for its Forwarder contract; it also provides transaction statuses including in progress, completed and refunded, so an integration can track a transfer through resolution.

For recurring payments, Mayan’s SDK documentation describes permanent deposit addresses tied to the destination chain, wallet and token. The team must use the address configured for the intended recipient and output asset; changing those details produces a different address.

The practical takeaway is to choose by asset pair and settlement terms, not by the word “bridge” alone. The exact route, quote and completion status remain specific to each transfer, and teams should verify them before treating destination funds as settled.