Slippage settings

Slippage is the price change caused by external market movements and not related to the user's operation within the pool. Slippage strongly depends on the liquidity volume inside the pool. If a token pool has low liquidity, significant changes in the exchange rate within the pool require less market movement.

In the settings, you can specify slippage (by default, the parameter is set at 0.5%) Slippage is a change in price caused by external market movements and not related to the user's activity in the pool. Slippage highly depends on the liquidity volume inside the pool. If a token pool has low liquidity, significant rate changes within the pool require less market movement.

CrossCurve users can configure the maximum permissible slippage for cross-chain operation:

In the field, specify the slippage for a single AMM operation (operations of adding, withdrawing, and exchanging in liquidity pools). A cross-network transaction may involve several AMM operations. In this case, the slippage is cumulative.

If during the execution of the operation, it is found that the slippage in one of the pools exceeds the user-set limits, the operation will be interrupted. Intermediate assets will be credited to the user's account. Although gas cannot be returned for an interrupted operation, interrupting the operation due to slippage can prevent much more significant loss of funds during exchange within the pool.

By default, the Slippage value is set at 0.5%. You can manually set the Slippage value. When doing so, we recommend considering the following recommendations:

• Setting an acceptable Slippage value too low may lead to the transaction being interrupted even at low pool volatility, resulting in gas waste when attempting the operation.

• Setting a high Slippage value opens up opportunities for front-running attacks and increases the risk of losses during high volatility of assets in the market.

Change the slippage parameter only if you clearly understand why you are doing it.