What Is Cross-Chain Slippage and How Do You Set It?

Cross-chain slippage is the difference between a quoted token conversion and the amount a swap leg actually delivers when it executes. The key condition is that a route can contain separate swaps on separate chains, so one slippage setting may not protect every leg in the same way. When comparing a route through Rango Bridge, check which conversion the quoted minimum applies to and what happens if another leg moves before it runs.

Slippage applies to execution, not the whole journey

Slippage tolerance sets how far execution may diverge from a quoted output before a swap reverts. For a single swap, a 0.5% tolerance on a quoted output of 100 tokens typically means a minimum output of 99.5 tokens; the contract checks that minimum when the trade executes.

A cross-chain route may have a source-chain swap, a cross-chain message or asset transfer, then a destination-chain swap. Each on-chain swap has its own execution conditions. A source swap can succeed and send the bridge asset while a later destination swap fails, depending on how the route is built. A slippage limit on the first swap does not automatically guarantee the final token amount.

That distinction matters because cross-chain execution is asynchronous. The source transaction may finalize before the destination transaction is submitted, leaving time for the destination pool price to change. Some routes deliver an intermediate asset on the destination chain if a final conversion cannot execute; others may have different recovery behavior. The route’s design determines which outcomes are possible.

Choose tolerance from the pool and execution delay

Set tolerance according to the swap leg’s liquidity, volatility, trade size and likely execution delay. For a deep pool and a modest trade, 0.1–0.5% is a common starting range. A thin pool, a volatile token or a large trade may need 0.5–1% or more to avoid routine reverts, but the wider bound also permits a worse fill.

Price impact and slippage are related but distinct. Price impact is the movement caused by your trade against current pool liquidity; slippage is the additional movement between the quoted state and execution. A route with 0.4% expected price impact does not become safe at 0.4% tolerance: fees, market movement and competing transactions can add to the realized difference.

For a route with two swaps, assess both legs independently. Tight tolerance on a source swap can prevent sending less bridge inventory than expected, while the destination swap needs room for its own pool conditions and delay. Widening both tolerances indiscriminately can compound the permitted loss across the route.

Work through the minimums before signing

Consider an illustrative route sending 1,000 USDC from Ethereum to SOL on Solana. Suppose the source conversion and route costs leave 998.8 USDC-equivalent units for the cross-chain transfer, and the destination quote is 5.20 SOL. With a 0.5% destination tolerance, the minimum output for that leg is 5.174 SOL, assuming the quoted amount is the amount the swap contract uses as its baseline.

The source swap has a separate minimum. If it quotes 1,000 USDC into a bridge asset, a 0.25% tolerance would set a source minimum of 997.5 units of that asset. The destination swap then calculates its own minimum from the amount actually arriving, not from the original 1,000 USDC. These numbers are examples; fees, decimals, transfer deductions and route logic change the actual baselines.

Before signing, inspect the quote’s final estimated output and minimum received, and identify whether the displayed minimum covers the destination conversion or only a source leg. If the route names a bridge or messaging layer such as Axelar, remember that cross-chain delivery and a destination DEX swap are different operations. A successful message can deliver the asset even when the later swap cannot meet its minimum.

Know what a failed leg means

If a swap transaction reverts because output fell below its minimum, that swap usually does not execute, though its network transaction fee may still be charged. A cross-chain route can be more nuanced: the source action may already be final, so a destination failure may require claiming, retrying, or manually swapping an intermediate token, depending on the protocol. On Solana, for example, transactions also expire when their recent blockhash is no longer valid, which can cause a submission to fail before execution; see the Solana transaction pipeline documentation.

Use this short check before authorizing the route:

• Compare quoted output with minimum received, and confirm which leg that minimum protects.
• Keep tolerance tight for deep, stable pools; increase it only for a reason visible in the route or market.
• Check the destination asset and whether a failed final swap leaves an intermediate token to recover.
• After source confirmation, verify the destination transaction and final token balance before repeating the route.