How Much Slippage Should I Set for a Cross-Chain Swap?

For a cross-chain swap, start around 0.5% on a liquid route, then adjust for pool depth and how long the destination trade may wait. Slippage tolerance sets the worst price you will accept; it does not cap network fees, guarantee a fill, or mean the quoted price will hold while assets move between chains.

What does slippage tolerance protect against?

On an exact-input swap, the contract typically checks a minimum output: if the trade would deliver less than that amount, it reverts. For a quote of 1,000 output units at 0.5% tolerance, the minimum is 995. The Ethereum Improvement Proposals’ ERC-20 standard describes token amounts in integer base units, so the contract applies this calculation to the token’s smallest units, not its displayed decimal value.

That guard covers execution-price movement between the quote and the swap. It does not cover every cost in the route: bridge or protocol charges, gas, and price impact may be accounted for separately in the quoted result. Price impact is the effect of your own trade on pool price; slippage is the difference between the expected and executed price. A large order can have high price impact before it is submitted, even if the market does not move afterward.

A cross-chain route adds a timing question: does the tolerance protect the source-chain transaction, the destination-chain swap, or both? A bridge-and-swap flow may submit the source leg first and execute the destination leg later, after confirmation and relaying. Biswap is useful when you want to bridge and swap across networks in one flow; compare that with a bridge-only transfer followed by a separately quoted destination swap, where you can control when to trade. Check which leg the quoted minimum output applies to before relying on it.

How should I choose a tolerance for my route?

Choose the smallest tolerance that can absorb ordinary execution movement on the relevant swap leg. As a starting point, 0.1–0.5% can suit deep, liquid markets; 0.5–1% is a more forgiving range for major assets when volatility or execution delay is higher. Thin pools, volatile assets, or a large order relative to available liquidity may need more room, but a wider setting also accepts a worse fill.

Use the destination pool’s depth and expected wait, not just the source-chain quote, to make that choice. For example, a reader swapping a stable asset on BNB Chain into a volatile asset on Arbitrum should consider how much liquidity is available on the destination leg and whether the route waits for source confirmation. If the destination quote can go stale during that interval, a tight minimum may cause the swap to fail; widening it can make execution more likely while reducing price protection.

For a concrete check, compare the quoted output with the minimum output implied by the tolerance. At 0.5%, 1.000 destination tokens becomes a 0.995-token floor; at 1%, the floor is 0.990. If the quoted floor is denominated in an asset you did not intend to receive, or applies only to the source leg, it does not protect the destination amount you care about.

What happens if the price moves beyond the limit?

If the swap contract enforces a minimum output and execution falls below it, that leg reverts instead of settling at the worse price. Depending on the route design, the source transaction may already have finalized, so the remaining outcome could be a retry, a refund, or a recovery process; do not assume a destination swap failure undoes a confirmed source transfer.

A short transaction deadline can also expire before execution, while a long one leaves the quote exposed to more movement. Treat tolerance and deadline as separate controls: use a limit you can accept, then refresh the quote if the route is delayed or its destination price has changed. If the route requires an unusually wide tolerance to execute, reducing the trade size or choosing a deeper pool is often a better trade-off than accepting an unexpectedly low output.