Set a tight output floor for liquid routes, then refresh the quote if the source transaction is delayed or market conditions change; widening slippage should be a deliberate price decision, not a way to force a stale trade through. In a cross-chain swap, your source-chain transaction and the later destination-chain execution can face different prices and timing. Treat the quoted destination amount as a condition to verify, not a promise that every route protects in the same way.
What does slippage tolerance protect?
Slippage tolerance sets how far execution may move from the quoted price before a swap leg fails. For an exact-input swap, the contract or route encodes a minimum output; if the executed amount falls below it, that leg reverts. Uniswap’s developer documentation gives 0.5% as an example tolerance, but the right value depends on the pair’s depth, volatility, and how long execution may take.
Price impact and slippage are related but different. Price impact is the movement caused by your trade against available liquidity at quote time; slippage is the additional movement between quoting and execution. A large trade can have high price impact even in a calm market, while a small trade can slip during a sudden price change or a congested block.
For a deep, liquid pair, a starting tolerance around 0.1–0.5% is a reasonable operating range; a thin or fast-moving pair may need more, but first check whether the displayed price impact already makes the trade unattractive. If the route exposes a minimum destination amount, compare it with what you would accept after all conversion legs. A generous source-leg tolerance does not necessarily raise a destination-leg minimum.
Why does a cross-chain quote go stale?
A cross-chain route may involve a source swap, a transfer or message, and a destination swap. These legs do not necessarily execute at the same moment: the source transaction must be included, and the destination action may wait on settlement or a relayer. Ethereum.org describes how a submitted transaction can remain pending before inclusion; cross-chain routes add another timing interval after the source-chain event.
That gap creates an important edge case: the source swap can succeed while a later destination swap fails its own minimum-output check. Depending on the route design, the destination asset may instead be delivered in a fallback form or require recovery. Read the route’s stated failure outcome before signing, and don’t assume one slippage setting governs every leg or guarantees the final token amount.
Quote age matters because it is the reference state for the route, not because a particular number of seconds is universally safe. If the quote has an explicit expiration, honor it; if it does not, refresh after a wallet delay, a fee adjustment, or a sharp market move. Acrossbridge searches often begin with a desire to save steps, but a single-flow service only helps if you still check the route’s minimum received amount and execution assumptions.
How should you set the limit in practice?
Use a worked example to separate the arithmetic from the route decision. Say a quote expects 1,000 USDC at the destination and you choose 0.3% tolerance for that output leg: the minimum is 997 USDC (1,000 × 0.997). If the route’s screen or transaction data shows a lower minimum, the route is allowing more downside than your chosen tolerance suggests; compare the actual minimum, not just the percentage label.
- Check the quote: record the expected output, minimum output, price impact, and any displayed expiry. Confirm the token and destination network are the ones you intend to receive.
- Set a tolerable floor: choose the lowest output you would accept after the route’s conversion legs. For liquid major pairs, start narrow; widen only if the route’s expected execution genuinely requires it.
- Submit promptly: avoid editing transaction fees or waiting through a market move while relying on the old quote. If you need to wait, request a fresh quote and recalculate the minimum.
- Verify both legs: after submission, distinguish source-chain inclusion from destination completion. A source transaction hash alone does not establish that the final asset arrived.
This is where acrossbridge changes the task for a frequent user: it lets you move and swap assets across chains in one flow, so you can assess the route as a combined operation instead of arranging each leg separately. That can reduce handoffs, but it does not remove the need to inspect the minimum received amount or account for time between chains.
When should you reject the quote?
Reject or refresh when the expected output has moved materially, the quoted minimum is below your acceptable floor, or price impact consumes most of the value you expected to receive. Increasing tolerance may turn a revert into execution, but it also authorizes a worse fill and can expose the trade to adverse ordering. Uniswap’s developer guidance recommends enforcing a minimum output rather than leaving it at zero.
A revert usually means the limit did its job: the swap did not meet the required output. It may still cost gas on the chain where the failed transaction ran, and a multi-leg route can have a different recovery path if an earlier leg already settled. Before retrying, check transaction status and the route’s failure handling; then obtain a fresh quote rather than resubmitting stale parameters. A larger tolerance is useful only when the additional downside is acceptable.
Questions after setting a cross-chain swap limit
Does higher slippage make a cross-chain swap faster?
No. A wider limit can reduce failures caused by price movement, but it does not shorten block inclusion, settlement, or destination execution. If speed matters, submit while the quote is current and use a route whose expected settlement fits your timing needs. Raising tolerance to compensate for a slow route accepts more price risk without guaranteeing faster delivery.
Can the source swap succeed if the destination swap fails?
Yes, depending on the route’s design. Cross-chain execution can separate source inclusion from destination execution, so inspect whether the route retries, delivers an intermediate asset, or provides another recovery path. Check the source and destination transaction states before sending another trade; repeating the route too early can create a second exposure while the first is still progressing.
Should I reuse the same slippage setting for every pair?
No. A deep stable pair, a volatile major-token pair, and a thin pool have different price impact and execution risk. Keep a narrow baseline for liquid routes, assess the quote’s expected impact and minimum output, then adjust only to a floor you would accept. If a thin route needs a very wide limit, reducing trade size or waiting for better liquidity may be the better choice.
For repeated transfers, save your own acceptable output floor by pair and size, then check it against each fresh quote. Acrossbridge can consolidate the cross-chain move and swap into one flow; your practical safeguard is still the minimum amount you are willing to receive at the destination.