Skip to main content
Splyt Genesis

Crypto markets, protocols and policy

Tight vs Loose Slippage on a Pool Bridge

For a liquidity pool bridge, set slippage tolerance just above quoted price impact; leave more room for large transfers or thin destination pools to avoid failed execution.

The Splyt Genesis Desk

Tight vs Loose Slippage on a Pool Bridge

Set slippage tolerance just above the price impact shown in your quote. On a cBridge xLiquidity transfer, the destination pool’s rate can move before execution, so the right margin depends on the quoted impact and the pool’s depth.

Read the quote, then choose

Quoted price impact: Start with the impact shown for your route. Your tolerance sets how much the rate can worsen before the transfer fails. Keep it just above the quoted impact so there is room for a small move, without accepting a much worse rate.

If the impact is already close to your tolerance, the rate can drift past the limit while the source chain reaches finality. The destination execution may then fail, and you may need to go through a refund step. A tight setting protects the amount you receive, but it leaves less room for the pool to move during that wait.

On cBridge, xLiquidity transfers are priced against liquidity pools on the destination chain. When checking a route, use the cbridge cross-chain details alongside the quote to identify the pool path before choosing your margin. The quote’s impact is the starting point; the pool’s depth helps you judge how much extra room to allow.

Transfer size versus pool depth: A transfer that is small relative to a deep pool generally needs less room. Stablecoins in deep pools usually suit a low tolerance, set just above the quoted impact. A large transfer takes more of the available liquidity, while a thin destination pool can move more for the same transfer size. In either case, leave a larger margin above the impact shown in the quote.

Cost of a failed attempt: Tight tolerance suits you if protecting the received amount matters more than avoiding a failed transfer and refund step. Loose tolerance suits you if getting through reliably matters more, and you accept that a moving pool may give you a worse rate. A looser setting can allow a transfer to execute after the pool moves, but it also permits more price movement before the transfer is rejected.

If the quoted impact is small and the destination pool is deep, choose tight. If your transfer is large relative to the pool, or the pool is thin, choose a margin above the quoted impact. Compare the amount at risk from a worse rate with the time and effort of a failed attempt before deciding how much room to leave.

Use the quote to set your tolerance, then adjust for transfer size and destination pool depth. That gives the pool rate room to move while limiting how much worse a rate you will accept.

Questions you may have next

Why does the same route show different price impact at different times?

Price impact changes when the amount of available destination-pool liquidity or the transfer size changes. A route can show a different impact even when you use the same networks and asset, so base your tolerance on the current quote.

Does slippage apply when bridging pegged xAsset tokens?

cBridge xAsset transfers use token mappings and mint or burn operations that are 1:1, so they do not have pool slippage. The tolerance choice here applies to xLiquidity pool transfers.

Can I change slippage after a transfer is submitted?

Set the tolerance before submitting. Once the transfer is submitted, changing the setting for a new transfer does not change the tolerance attached to the one already in progress.