4 Checks for Cross-Chain Swap Slippage

Slippage tolerance is the largest drop you will accept between a swap’s quoted output and the minimum output allowed at execution. The key condition is whether the quote’s final amount reflects every swap in the cross-chain route: a bridge fee alone does not tell you how much the destination token may change.

Tolerance sets the minimum output the swap can accept

A tolerance of 0.5% on a quote of 1,000 destination tokens sets a minimum of 995. If the swap would return 997 when it executes, it can proceed; at 994, it should fail rather than accept less than your limit. The setting is a threshold, not a promise that you will receive the quoted amount.

A direct bridge route can move the same asset between networks, while a route found through bungee bridge may include a swap before or after the bridge. In the second case, check the quoted destination amount and its minimum, since those reflect the swap exposure more directly than the bridge fee. The route may apply slippage controls differently on each leg, so confirm what the transaction screen says your tolerance covers.

Price movement and route execution determine the result

Slippage is the difference between the quote and the execution price; price impact is the effect your trade size has on available liquidity. A large swap in a shallow pool can have high price impact before the transaction is sent, while prices can move after the quote because of other trades, network delay, or competing transactions.

Cross-chain execution can involve a source-chain swap, a bridge transfer, and a destination-chain swap. The destination swap may happen later than the source transaction, so its market conditions can change while the transfer is in flight. Depending on the route, a failed destination swap may leave funds in an intermediate token or require a recovery action; check the route’s stated failure handling before sending.

For example, suppose a quote shows 1,000 USDC at the destination. At 0.5% tolerance, the minimum is 995 USDC; if the pool moves and execution would return 994, the swap should stop. Raising tolerance to 2% lowers the minimum to 980, making execution more likely but allowing up to 20 fewer USDC than quoted. Tolerance is not a fee, though accepting a worse output can cost more than the bridge fee.

Four checks help set tolerance and submit safely

1. Review the route. Confirm the source and destination networks, tokens, and quoted final amount. Check whether the route swaps before, after, or on both sides of the bridge.
2. Read the minimum output. Compare it with the quote in destination-token units. If the minimum is too low for you, reduce tolerance or choose a route with a more suitable quote.
3. Set tolerance for the trade. Use the route’s suggested value as a starting point, then consider the token’s volatility, pool liquidity, and execution delay. A tighter limit protects the minimum you accept but makes a revert more likely; a wider one improves the chance of execution at a worse price.
4. Check the result on both networks. After submitting, use the transaction status to confirm the bridge transfer and destination swap completed. If the route reports a failed or pending destination step, follow its stated recovery process before trying the transfer again.