Search docs
Search vfat.io documentation

Auto-Exit

Auto-Exit closes a position automatically once the pool’s price crosses a trigger you configure. It’s useful as a stop-loss/take-profit for a position without having to watch it.

Auto-Exit settings, with lower/upper bound triggers and exit tokens

Setting bounds

You can set a lower bound, an upper bound, or both:

  • Lower only: exit if price drops below your trigger
  • Upper only: exit if price rises above your trigger
  • Both: exit on either

For each bound you choose the token you want to receive on exit, defaulting to the chain’s native token and a trigger price around the current market price. If a bound you set is already true at the current market price, vfat.io warns you before saving that the position may exit as soon as automation next runs.

Slippage and price impact

As with other automations, Auto-Exit lets you set a price-impact and slippage tolerance for the swap executed on exit.

A trigger price determines when an exit becomes eligible; it does not guarantee an execution price. Execution also depends on a successful quote and simulation, your limits, and sufficient fee revenue or eligible prepaid gas. Check the threshold estimate and automation status in the position’s settings.

Availability

Auto-Exit is configured per position. Both regular LP positions and concentrated-liquidity (NFT) positions have their own configuration form, since NFT positions track a price range rather than a single token amount. It’s available wherever the chain’s Sickle contract version supports it; on chains where it isn’t yet available, the option is shown as unavailable rather than hidden.

Like other automation types, enabling Auto-Exit for the first time on a chain requires enabling the general Automation setting for that chain first.