Skip to main content
Orchestrate is a swap with an instruction attached. The funds and a payload travel together, and your contract on the destination chain reads that payload and acts on it the moment the funds land. Entering a protocol from another chain normally takes four separate user actions: move funds across, swap into the right asset, switch apps, deposit. Orchestrate collapses all four into the one signature the user already gives to swap.

How it works

Request a quote that supports payloads, then pass the bytes to the swap call. Mayan forwards them verbatim; decoding them is your destination logic’s job.
What you can attach:
  • Deposit. Funds arrive and go straight into a protocol or vault.
  • Stake. Assets are staked on arrival, so users start earning without a second step.
  • Mint, join or participate. The transfer triggers it as the funds land.
  • Your own logic. Encoded contract calls, IDs, session data, or routing information your app needs.

Requirements

Orchestrate is the one part of Mayan that is not a drop-in:
  • Destination logic that can receive the funds and decode your payload.
  • A route that carries payloads. Not every route does, which is why the quote request has to ask for one.
  • Small payloads. Each chain and route has its own message-size limit.
See Zaps for the payload format and per-chain behavior.

Where it fits

  • A vault turns a multi-step entry into one click.
  • A yield app puts deposits to work the moment they land.
  • A trading app funds a position and opens it in the same action.

Next steps

Zaps

Payload format, and which routes carry one.

Executing Swaps

Passing the payload argument on EVM, Solana and Sui.