Why cross-chain swaps can deliver less than quoted

Cross-chain swap slippage is the difference between the amount a route quotes and the amount you receive when it completes. It matters because a swap across two networks can involve several steps, and the prices or available liquidity can change before each one runs.

A route may swap your asset on the source network, move value across a bridge, then swap again on the destination network. The exact steps depend on the route shown by the swap interface. Each trade can use a different pool, where traders swap tokens, and a thin pool may give you a worse rate for a larger trade. A bridge moves assets or messages between networks; it does not guarantee that the same token or trading conditions exist at the destination. For the separate question of which destination tokens support WBTC, see Acrossbridge WBTC destination support. That token support question is distinct from the route’s slippage estimate.

What makes slippage change on a cross-chain swap?

Slippage can change when the trade moves the pool price, when other trades happen first, or when the route takes longer to complete. The swap screen’s quote is an estimate based on the route and market conditions at that moment. A later transaction may execute at a different rate, especially if the route waits for activity on more than one network.

Fees also affect how much arrives, but they are not the same as slippage. The route preview may list network fees, bridge fees, or a swap fee separately. Compare the quoted output and the fees as separate parts of the cost; a lower slippage setting does not remove fees.

How should I read the quoted amount and minimum?

The quote shows an expected amount. The minimum received is the lowest amount the transaction is set to accept under its slippage limit. If the final output falls below that minimum, the swap may fail instead of completing at a worse rate. Check the interface’s route details, since it may show several steps and separate amounts.

• Compare the expected output with the amount you send, not just the headline exchange rate.
• Check the minimum received and the slippage setting before confirming.
• Look for fees and the destination token in the route details.
• If the quote changes while you review it, refresh it and read the updated minimum.

Raising the slippage limit can let a transaction complete after a larger price move, but it also lets you receive less than the original quote. It does not improve the price or make the route faster. Use the limit shown by the interface as a boundary you understand, rather than increasing it just to make a failed swap go through.

What is the practical way to reduce slippage?

For most readers, the better choice is to compare the route’s expected output, minimum and fees, then use a route with enough liquidity for the trade. A smaller trade can have less price impact in a shallow pool, though the displayed quote and fees still matter. If the minimum looks too low or the token does not match what you intend to receive, pause and review the route before confirming. Slippage is a property of the route and its conditions, not a fixed charge you can predict from the network alone.