Cross-Chain Slippage: What Is It and How Does It Work?
Cross-chain slippage is the difference between a route’s quoted output and the minimum output its execution will accept; a 0.5% tolerance permits up to 5 units of loss for every 1,000 units quoted. It matters when a transfer includes a swap, because prices and available liquidity can change between the quote and the moment each trade executes.
What does the slippage limit protect?
The limit is an execution condition, not a promise that the destination amount will equal the quote. A router or settlement contract checks that a swap returns at least its configured minimum; if it returns less, that swap reverts. That protects against accepting an unexpectedly poor price, but a revert can leave a multi-step route incomplete or trigger whatever refund behavior the route supports.
Keep three quantities separate when comparing routes: the quoted output, the minimum acceptable output, and the fees already deducted from the quote. Slippage tolerance should cover possible price movement during execution, not disguise a route’s fees or compensate for comparing different destination tokens. Uniswap’s v2 documentation describes the same core swap guard through a minimum output amount; the exact contract and failure handling depend on the route.
How does a cross-chain route apply the bound?
A route with swaps can have multiple execution points. For example, a transfer might swap the source token into a bridge asset, transfer that asset across chains, then swap it into the destination token. Each swap can face its own pool price movement; bridge fees and destination gas are separate deductions, and a bridge quote may have its own expiry or fill conditions.
Some systems allocate a total slippage budget across swap legs; others expose separate bounds or enforce a final minimum. If 0.5% is split evenly over two legs, each leg gets 0.25%. In the simplified case where both legs reach their full allowance, the combined reduction is about 0.4994%, since the factors multiply: 0.9975 × 0.9975. A single 0.5% bound on each leg could allow nearly 1% combined.
That distinction matters when using a bungee bridge aggregator to compare routes. Check whether the quoted minimum describes the final destination amount or just an intermediate swap: an intermediate minimum does not, by itself, cap all later price movement. For the transfer and swap described here, the Bungee bridge aggregator is one way to find and compare cross-chain routes; inspect how each candidate represents its output floor before choosing.
How should you choose a tolerance?
Set the bound from the route’s execution risk and your acceptable loss, not from a universal “safe” percentage. A deep, stablecoin pool may support a tighter tolerance than a thin pool or a volatile token pair; a route requiring source and destination swaps has more price-sensitive steps than a transfer with no swap. A tighter bound reduces the worst price you will accept but increases the chance that one leg reverts after conditions move.
For an illustrative calculation, suppose a route quotes 996.4 USDC on the destination for 1,000 USDC sent, after its estimated fees. At 0.5% tolerance on the final output, the floor is 996.4 × 0.995 = 991.418 USDC. That bound allows about 4.982 USDC of movement from the quote; it does not mean the route’s fee is 0.5%, nor does it guarantee that the transfer will complete.
When evaluating the quote, confirm the token addresses and decimals on both chains, whether the displayed output is before or after fees, and whether the minimum is end-to-end or per leg. Also note quote age: source-chain inclusion, confirmation or finality, and destination execution can be separated in time. Ethereum’s documentation distinguishes inclusion from finality; a quote based on one state can become stale while a transaction waits for inclusion or while a bridge waits for its settlement condition.
What happens when execution misses the bound?
If a swap leg cannot meet its minimum, it typically reverts rather than executing at a worse price. Depending on the route, the original asset may be refunded, funds may remain recoverable on one chain, or a destination-side recovery path may be needed. Read the route’s stated failure behavior before sending a material amount, especially when there are multiple swaps or a contract action after arrival.
For a bungee bridge comparison, prefer a route whose destination minimum and failure path are clear over one that merely shows the largest headline estimate. Match the tolerance to the weakest liquidity leg and the time the route needs to execute; then compare fees, expected delivery, and recovery behavior separately.