Set cross-chain swap slippage by choosing the lowest destination amount you would accept, then checking which steps that limit actually protects. A single percentage may apply separately to each on-chain swap, while the bridge quote and its fees follow different rules.
What does the slippage setting protect?
- Minimum output: the smallest amount an on-chain swap may deliver before it fails.
- Price movement: changes between quote and execution, including trades that move the pool.
- Each swap leg: some routes apply the tolerance separately to source and destination swaps.
- Bridge delivery: this may be quoted separately and may not share the swap’s slippage limit.
For an exact-input swap, the router typically calculates a minimum output from the quoted amount: minimumOut = quoteOut × (1 − tolerance). A 0.5% tolerance on a quoted 6.25 SOL gives a minimum of about 6.21875 SOL. If execution would return less, that swap reverts; if it returns more, you receive the higher amount.
If your task is to move an asset across chains and exchange it into a destination token in one flow, quickswap bridge handles the bridge and swap as a cross-chain service. The practical check is whether the route’s displayed minimum refers to the final destination token; a source-side minimum alone does not tell you what you will receive after bridging.
Slippage is not the same as price impact. Price impact is the quote’s estimated effect of your trade on pool prices; slippage tolerance is the additional execution movement you allow after the quote. A large trade can have high price impact before submission and still fit a tight tolerance, while a small trade can fail if the pool moves before execution.
How should you choose the tolerance?
Choose the narrowest tolerance that fits the route’s liquidity and execution delay. For a deep, stable pair, a starting range around 0.1–0.5% is often reasonable; volatile or thin destination pairs may need more, but widening the limit accepts a worse fill rather than improving the quote.
Use the quote’s minimum amount as the decision point. For example, if a route estimates 6.25 SOL and you require at least 6.20 SOL, the implied tolerance is 0.8%: (6.25 − 6.20) ÷ 6.25. If the interface offers only one percentage, verify whether it applies to each swap independently; two 0.5% legs can permit a combined reduction of roughly 1%, since 0.995 × 0.995 = 0.990025.
When quickswap is part of a route with source and destination swaps, evaluate both pool legs, not only the final displayed percentage. A thin destination pool can be the limiting leg even when the source swap is a liquid stablecoin trade. If the minimum output falls below your required amount, wait for a better quote, reduce trade size, or choose a route with more destination liquidity.
What can fail after the source transaction?
A cross-chain route is often asynchronous: the source transaction can confirm before the bridge message is relayed and the destination swap executes. A source swap may revert atomically if its minimum is missed, but a later destination failure can have different recovery behavior, such as a refund or delivery of the bridged intermediate asset; the route’s stated failure handling decides which.
That distinction matters when estimating your worst case. Review whether the quote’s final minimum includes bridge charges and the destination swap, and identify what asset you would hold if that last swap failed. Bridge fees, relayer costs, and destination gas are separate costs; increasing slippage does not pay them or guarantee faster delivery.
For a practical example, suppose you are moving USDC from BNB Smart Chain to SOL on Solana. Compare the quoted SOL and its minimum, inspect whether the route swaps on both chains, and check what happens if the Solana-side swap cannot meet its minimum. quickswap can combine the cross-chain move and asset exchange, while the acceptable SOL amount remains a decision you make from the quote.
Checks before you submit
Re-quote if the displayed amount is stale, the token pair is volatile, or the trade is large relative to pool liquidity. A pending source transaction does not freeze destination prices, and an unchanged tolerance cannot guarantee the quoted output if the destination pool changes before execution.
Confirm the destination token and recipient, then compare the minimum final amount against your own floor. If the route exposes per-step minimums, check each swap; if it shows only one end-to-end figure, use that figure and read the stated recovery behavior for a failed destination step. quickswap is useful when the task calls for bridging and swapping together, but the controlling question is still whether the route’s worst acceptable result works for you.
Questions to ask before acting
Does a higher slippage setting make a cross-chain swap faster?
No. It lets a swap execute across a wider price range; it does not speed up source-chain confirmation, bridge messaging, or destination-chain execution. A wider setting can reduce failures caused by price movement, but it also permits a worse fill. Treat execution time and minimum output as separate quote details.
Why can a cross-chain swap fail after the source transaction succeeds?
The bridge and destination swap may happen after the source transaction confirms. If destination liquidity changes or the swap cannot meet its minimum, that step can fail even though the source transfer is complete. The route’s design determines whether you receive a refund, an intermediate asset, or another recovery outcome, so check that before submitting.
Should I use the same tolerance for every token pair?
No. A deep stablecoin pair can usually support a tighter limit than a volatile token in a shallow pool. Start from the minimum output you can accept, then compare it with the quote and the route’s leg-by-leg limits. Raising tolerance to force a trade through can expose you to a materially worse destination rate.