Set Slippage by Swap Leg, Not by Guesswork

A 1% slippage limit means you accept receiving as little as 99% of the quoted output for the swap it covers. For a cross-chain swap, set that limit around the actual swap leg and check what happens if another leg cannot complete.

Slippage is the difference between the output shown in a quote and the output when a trade executes. A tolerance sets the worst price movement the transaction will accept. It does not guarantee you will receive the quoted amount, and it does not make a thin or volatile route safe.

A cross-chain route can combine a swap on the source chain, a bridge transfer, and a swap on the destination chain. Some routes swap on only one side. The relevant tolerance depends on where the trades happen and how the route handles a failed or delayed step. For more on assessing route depth, see this comparison of Wormhole bridge route liquidity.

What does slippage cover in a cross-chain swap?

Slippage usually limits the execution price of a swap, rather than the entire cross-chain journey. A bridge transfer may move a fixed token amount, while a source or destination exchange converts that amount through a liquidity pool.

Check the quote for the estimated output and the minimum output. The minimum is the floor the swap is designed to accept after applying its slippage setting. If the market moves past that floor before execution, the swap may fail or follow a route-specific recovery process.

Some interfaces expose one slippage setting for the route. Others let the route provider set or calculate limits for individual swaps. A single number on the screen may not describe every stage, so inspect the route details before signing. In particular, find out whether the displayed minimum applies to the destination token you want, or only to an intermediate token.

How should you choose a slippage setting?

Choose the narrowest tolerance that still gives the route a reasonable chance to execute. Start with the quote’s expected output, then consider the liquidity and volatility of the pools used for each swap.

A deep pool usually absorbs a trade with less price movement than a shallow pool, all else equal. A large trade relative to available liquidity can move the pool price even before the transaction reaches it. A volatile token pair or a route that takes time to complete adds more chance for the market price to change.

For a stable, liquid pair, a tight limit may be appropriate. For a thin pool or a volatile asset, a slightly wider limit may reduce failures, but it also permits a worse execution price. Do not widen it simply because a transaction failed: first check whether the quote is stale, the route is congested, or the pool cannot handle the trade at an acceptable price.

Compare routes using more than the headline output. Check which chain and pool each swap uses, whether the path is split across pools, the expected arrival amount, fees, and the time estimate. A route with a higher displayed output can still be a poor choice if its liquidity is shallow or its minimum acceptable output is unclear.

• Trade size: Larger trades can cause more price impact in a given pool.
• Pool depth: Thin liquidity leaves less room for price movement before the minimum is crossed.
• Market movement: Fast price changes can make a valid quote outdated before execution.
• Route timing: A longer transfer can leave more time for conditions to change before a later swap.

What should you check before approving?

Before signing, check the final token, estimated output, minimum output, and which parts of the route actually swap. A quoted amount is an estimate; the minimum output shows the boundary the route is meant to enforce.

Also check the route’s failure behavior. Depending on the protocol and stage, a failed destination swap may leave tokens available for recovery, require another transaction, or behave differently from a source-chain swap that reverts. Do not assume that “the swap failed” means every earlier step was undone. Read the route’s stated recovery instructions and make sure you can access the destination chain if needed.

Use this sequence when comparing a route:

1. Confirm the source and destination tokens, including that the token representations are the ones you intend to receive.
2. Read the route steps and identify every swap, bridge transfer, and intermediate token.
3. Compare the quoted output with the minimum output, and decide whether that floor is acceptable to you.
4. Review fees, timing, and failure or recovery handling before signing.

The practical rule is simple: set slippage for the swap that needs it, and judge the route by the minimum you are willing to receive. A wider setting can help a trade execute during movement, but it buys that chance by accepting a worse price. If the quoted minimum is unacceptable, choose another route or reduce the trade size.