Add and Remove Liquidity

Quickly Add or Remove Liquidity with the Telegram Bot #

Join the Fatsale official community for questions and feedback.

Major Swap platforms are increasingly reducing support for V2 pools, and adding liquidity for tokens with tax or other mechanisms can be troublesome. Network conditions also vary across users, which may cause liquidity operations to fail. For this reason, Fatsale supports quick V2 liquidity adding and removal inside the bot. After creating a token, you can add liquidity directly without switching back and forth between multiple pages.

1. Start the Bot #

Click this link, or search for @FatToken_bot in Telegram, then click Start.

2. Open the Token Detail Panel #

Enter your token contract directly in the input box. The bot will query on-chain token information and return the token detail panel. Then click Add Liquidity or Remove Liquidity to enter the corresponding page.

At this point, you need to have already created or imported a wallet. For details, see the bot token creation guide.

3. Add Liquidity #

After clicking Add Liquidity in the token detail panel, the bot opens the liquidity adding panel. The panel displays the current pool state, including:

  1. Current base-token information.
  2. Current token information.
  3. Whether the token already has liquidity.
  4. The amount of each token currently in the pool.
  5. The selected wallet information.
  6. The amount of token you want to add into the pool.
  7. The amount of base token you want to add into the pool.
  8. Transaction slippage.

You can use the buttons below the panel to modify all liquidity-adding parameters:

  1. Switch chain.
  2. Switch wallet.
  3. Switch exchange.
  4. Set base token: choose an existing token or enter a token contract.
  5. Set pool token: choose the token you want to use as the pool-side token.
  6. Set slippage: if slippage is too high, bots may front-run the add/remove liquidity transaction and cause losses. Adjust slippage carefully, or use private liquidity operations.
  7. Use WBNB: for example, LP reward templates may not support adding liquidity with BNB before trading is opened. If this option is enabled, the bot first sends a transaction to convert BNB to WBNB, then uses WBNB to add liquidity.
  8. Start adding liquidity: the bot automatically determines whether approval is required and sends the approval transaction first. You only need to confirm once to complete the operation.
  9. Private add liquidity: the transaction is submitted through a private node. Because of the private node, sniper bots cannot see the transaction and cannot front-run it. Private transactions may be delayed by 3-4 blocks, so this is strongly recommended when timing is not extremely sensitive.

4. Remove Liquidity #

After clicking Remove Liquidity in the token detail panel, the bot opens the liquidity removal panel. The panel displays the current pool state, including:

  1. Current base-token information.
  2. Current token information.
  3. Whether the token currently has liquidity.
  4. The amount of each token in the pool.
  5. The selected wallet information.
  6. The maximum removable liquidity of the current wallet.
  7. The percentage the user wants to remove, with the removable token amount calculated automatically.
  8. Transaction slippage.

You can use the buttons below the panel to modify all liquidity-removal parameters:

  1. Switch chain.
  2. Switch wallet.
  3. Switch exchange.
  4. Set base token: choose an existing token or enter a token contract.
  5. Set pool token: choose the token you want to use as the pool-side token.
  6. Set slippage: if slippage is too high, bots may front-run the add/remove liquidity transaction and cause losses. Adjust slippage carefully, or use private liquidity operations.
  7. Receive WBNB: sometimes liquidity for BNB-paired tokens cannot be withdrawn directly as BNB. Enable this option to receive WBNB after liquidity removal, then swap WBNB back to BNB on a Swap.
  8. Start removal: the bot automatically determines whether approval is required and sends the approval transaction first. You only need to confirm once to complete the operation.
  9. Private remove liquidity: the transaction is submitted through a private node. Because of the private node, sniper bots cannot see it and cannot front-run it. Private transactions may be delayed by 3-4 blocks, so this is strongly recommended when timing is not extremely sensitive.