Set Slippage by the Swap Legs in a Cross-Chain Route

Set slippage against the swap legs in a cross-chain route, then check what the bridge quote and destination minimum actually guarantee. A cross-chain swap can include a source-chain swap, a bridge transfer and a destination-chain swap. Those steps may have separate execution conditions. One percentage in a wallet interface does not necessarily cap the total difference between the displayed quote and the amount that arrives.

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

Slippage tolerance usually sets the worst execution price a swap transaction will accept. For an exact-input swap, the quoted output is used to derive a minimum output, often represented in the transaction as amountOutMin or a similarly named field. If the swap cannot meet that floor when it executes, the swap reverts.

That floor applies to the contract call that enforces it. A bridge transfer is not automatically covered by an AMM swap’s minimum-output check. The bridge may have its own quote, fees, liquidity conditions and settlement rules. Some routes swap before bridging, some after, and some on both sides. Read the route’s steps and inspect which minimum applies to each one. A ParaSwap cross-chain route comparison offers more detail on how route choice changes the transfer.

For an exact-output transaction, the constraint may instead be a maximum input: the transaction must not spend more than the encoded cap to obtain the requested output. The interface’s slippage percentage is only useful if you know which on-chain condition it controls. Check the quote details or transaction data when the interface does not make that clear.

How should you choose the tolerance?

Choose the narrowest tolerance that still reflects the route’s likely execution conditions. The quote’s price impact comes from trading against available liquidity; slippage is the difference between the quoted and executed price as conditions change before execution. A thin or volatile pool can move more than a deep, stable one, but widening tolerance does not improve the route. It only permits a worse execution if the transaction reaches that point.

Start with the quoted output, minimum received, price impact and route composition. Consider whether the source and destination swaps each use a separate pool, whether the quote can expire, and whether the transaction may wait for block inclusion. If a global setting is applied independently to two swap legs, each leg may consume its own tolerance. The combined output can therefore fall farther below the original quote than the percentage suggests.

Use these checks before signing:

• Identify every swap leg and the token pair each one trades.
• Compare the quoted output with the encoded minimum output for each swap.
• Read the bridge quote separately, including its fees, destination amount and any expiry or execution conditions.
• Confirm what happens if a later step fails, such as whether the route reverts, refunds, or leaves a claim or recovery action.

A stablecoin route can still have material price impact if liquidity is fragmented or the trade is large relative to the pool. Conversely, a volatile pair may have deep liquidity. Set tolerance from the route and amount, not from a token label or a preset that you carry between transfers.

What can go wrong when tolerance is too tight or too wide?

A tolerance that is too tight makes a swap revert when the pool price moves beyond its minimum-output condition before execution. That protects the swap from settling below the floor, but a reverted transaction may still consume gas on the source chain. In a multi-step route, the failure point matters: a source swap can complete before a bridge transfer, while a destination swap may execute only after the bridge settles. The route’s recovery behavior depends on its contracts and provider path.

A tolerance that is too wide accepts a lower output than the quote may lead you to expect. For on-chain swaps, a loose minimum also leaves more room for adverse execution, including sandwiching around a visible transaction. It cannot force a bridge to deliver a particular amount if that bridge’s own quote or destination conditions govern settlement.

Do not use a broad tolerance to push through a route whose minimum received is unclear or whose bridge quote has changed. Refresh the quote, compare the full destination amount after fees, and inspect the failure path. If the route requires a materially lower minimum than the quote implies, choose a different route or wait for conditions to change.

The practical rule is simple: approve the route only when its per-swap minimums and bridge terms match the amount you are willing to receive. Treat the displayed slippage setting as one transaction parameter, not a guarantee for the entire journey across chains.