Set Cross-Chain Slippage Against the Route’s Minimum Output

Set the slippage tolerance to the narrowest band that lets the quoted route execute at its minimum output. A cross-chain swap can involve a source-chain swap, a bridge transfer and a destination-chain swap, each with different execution conditions. The percentage is a limit on acceptable output change where the route applies it; it is not a forecast of the price you will get. Start with the quote’s minimum received amount and identify which execution step the tolerance protects.

What does slippage tolerance control in a cross-chain swap?

Slippage tolerance sets a floor for the output of a swap step. If that step cannot meet its minimum output when it executes, the transaction may revert or follow a protocol-specific failure path. In a cross-chain route, the source and destination steps do not necessarily execute together or share one on-chain transaction. The route may apply a bound to one swap, to multiple swaps, or use another execution rule. Check the quote and transaction details to see which output the displayed tolerance constrains.

A quoted amount and a minimum amount answer different questions. The quote estimates what the route expects to deliver at the time it is requested. The minimum is the least output allowed under the configured bound. If the tolerance is expressed as a percentage of the quoted output, a 1% tolerance would set a floor at 99% of that amount. That example describes the arithmetic, not a recommended setting. Network fees, bridge fees and other deductions can also affect the final amount, so compare like with like: the quote’s stated net output against its stated minimum.

For a fuller explanation of the stages and handoffs, the mayan bridge account traces how a cross-chain swap proceeds. Here, the practical point is that time between quoting and execution can matter. A source transaction may confirm before a destination swap runs, and the route may depend on liquidity and prices still being available at that later step.

How should I choose a tolerance for the route?

Choose a tolerance based on the route’s weakest execution step, not on a universal rule. A deep, stable market may support a tighter bound than a thin pool or a volatile token pair. A longer or more complex route can add more opportunities for the quoted output to change before completion. The interface’s suggested setting can be a starting point, but the displayed minimum received amount is the decision point: decide whether that amount is acceptable before signing.

Use these checks before submitting:

• Read the net minimum. Confirm how many destination tokens the route guarantees at its minimum, after the fees shown in the quote.
• Inspect each swap leg. Look for separate source- and destination-chain swaps, and note whether the tolerance applies to one leg or the whole route.
• Consider liquidity and volatility. Thin liquidity, a large trade relative to the pool, or fast price movement can widen the gap between quote and execution.
• Compare the wider band with its cost. A wider tolerance can reduce failures caused by price movement, but it also permits a worse execution price up to the stated minimum.

Do not widen the setting just to make a transaction go through without checking why it failed. The cause may be a stale quote, insufficient liquidity, an unavailable route or a destination-side execution constraint. Raising tolerance addresses only some price-bound failures. It does not add liquidity or guarantee that the route will complete.

What happens when the destination swap misses its minimum?

The result depends on the route’s failure handling. A destination swap that cannot meet its minimum may fail even after the source transaction has succeeded. Some designs provide a refund, recovery or retry path; others can leave the user with an intermediate asset that needs a separate action. The route’s transaction details and failure instructions determine which case applies. Review them before signing, especially when the destination asset differs from the bridge asset.

That distinction also separates slippage from bridge risk. A tolerance bounds execution price for a swap where the protocol enforces that bound. It does not, by itself, guarantee message delivery, completion time, refund behavior or the value of an intermediate asset. Those properties come from the route’s contracts and failure design. Treat them as separate parts of the transaction rather than assuming a generous percentage solves every failure mode.

When should I cancel and request a new quote?

Request a fresh quote when the displayed minimum no longer fits the trade, the route changes, or the interface reports that the quote has expired. If the trade only clears after a much wider tolerance, reassess its size or wait for conditions to change. Splitting a large trade may reduce its price impact when the route’s liquidity supports smaller executions, though extra transactions can add fees and operational steps. Check the minimum for each new quote rather than carrying over the previous setting.

For most users, the better choice is a tight, route-specific tolerance that leaves the displayed minimum acceptable. Widen it only when the route’s execution conditions justify the additional price range, and understand what happens if a later leg fails. That keeps the setting tied to the amount you are willing to receive, while making clear that tolerance is one execution limit, not a guarantee of cross-chain completion.