Counter anti-bot measures
Be careful ! Antibot protections cannot be bypassed.
But we have implemented many parameters to avoid them.
BUY/SELL TAX checker
⚠️ Available on BSC / AVAX / FTM only ⚠️
LimitSwap is now able to calculate buy and sell taxes on token
CONFIGURATION
new options in tokens.json:
- "BUY_AND_SELL_TAXES_CHECK": "true"
- "MAX_BUY_TAX_IN_%": "20"
- "MAX_SELL_TAX_IN_%": "20"
HOW TO UNDERSTAND IT
Bot will not buy/sell if Tax is above those values
--> with MAX_BUY_TAX_IN_% = 20, bot will not BUY if tax > 20%
DOES IT SLOWS DOWN THE BOT?
Yes, since it needs to call a smart contract to calculate Tax...
BUYAFTER_XXX_SECONDS
SELLAFTER_XXX_SECONDS
Sometimes the team will tell you "99% tax if you buy in the 2 first blocks", or "99% tax during 1 minute after launch"
--> use this option to ask the bot to wait for XXX seconds before making BUY order.
FYI: 1 block = 3s on BSC, and 13s on ETH
START_BUY_AFTER_TIMESTAMP
START_SELL_AFTER_TIMESTAMP
Sometimes the team will tell you "99% tax if you buy before XXXX timestamp"
--> use this option to ask the bot to pause before time reach this timestamp.
Use https://www.unixtimestamp.com/ to define value
MULTIPLEBUYS / BUYCOUNT
Sometimes the team will tell you "You can only buy a maximum of XXXX tokens" or "You can only buy a maximum of XXXX BNB / ETH / AVAX... of token"
--> use this option to buy multiple times this small amount
CONFIGURATION
in tokens.json, MULTIPLEBUYS has now 2 options :
Option 1 : buy with the same wallet
"MULTIPLEBUYS" : "same_wallet"
"BUYCOUNT": (as many buys as you want)
Option 2 : buy with different wallets (the wallets you configured in settings.json)
"MULTIPLEBUYS" : "several_wallets"
"BUYCOUNT": (maximum 5 buys, because there are 5 wallets in settings.json)
CHECK IF TRADING IS ENABLED
Sometimes liquidity is added but trading is not yet enabled. Team will enable trading later with a "EnableTrading" option. In this case, if you don't use options below, the bot will try to buy when trading is not enabled, resulting in a "TRANSFER_FAILED" error. The difficulty is the fact that there are many ways to enable trading, so it is very difficult for the bot to detect it.
Option 1 - CHECK_IF_TRADING_IS_ENABLED
(available on BSC / AVAX / FTM only)
In tokens.json : CHECK_IF_TRADING_IS_ENABLED = true
--> bot will check if trading is enabled after it detects liquidity.
Option 2 - "WAIT_FOR_OPEN_TRADE"
This option can detect EnableTrading in 2 ways :
1/ The bot scans pending transactions, and detect the methodID of EnableTrading functions that we have implemented in the code --> It's faster, but we need to implement in the code as many ways to do EnableTrading as wa can, and it's impossible to guarantee that the team will not use an unknown way to Enable Trading 2/ The bot waits for the price to move before making an order --> It's a "universal" way to detect that trading is enabled, but your sniping will be a little bit slower, since you need to wait for someone to buy before you.
There are 4 options:
| WAIT_FOR_OPEN_TRADE value | Description |
|---|---|
true_after_buy_tx_failed | 1/ Bot detects liquidity 2/ Bot try to make a BUY order 3/ If Tx fails, bot will launch wait_for_open_trade With this option, bot will do 2 tests at the same time : 1/ Scan pending transactions 2/ Wait for the price to move --> it will BUY if :
|
true | Same as "true_after_buy_txfailed", but bot won't even try to make a Tx after it detected liquidity --> it will directly enter in WAIT FOR OPEN TRADE mode |
mempool_after_buy_tx_failed | 1/ Bot detects liquidity 2/ Bot try to make a BUY order 3/ If Tx fails, bot will launch wait_for_open_trade
With this option, bot will do 1 test only :
1/ Scan pending transactions
--> it will BUY if it detects an openTrading Tx |
mempool | Same as "mempool_after_buy_tx_failed", but bot won't even try to make a Tx after it detected liquidity --> it will directly enter in WAIT FOR OPEN TRADE mode |
Examples of Tx that the bot will detect : openTrading / enableTrading / tradingStatus
WAIT_FOR_OPEN_TRADE": "true_after_buy_tx_failed" is the team recommandation 👍
In our opinion, this is the best option because you never know if the team will use this antibot protection or not. This option guarantee you the best speed (if first BUY tx works) and security.
⚠️⚠️ BE CAREFUL ⚠️⚠️ To make "WAIT_FOR_OPEN_TRADE": "true" or "true_after_buy_tx_failed" work, you need to snipe on the same liquidity pair that liquidity added by the team Why ? Because if you try to snipe in BUSD and liquidity is in BNB, price will move because of price movement between BUSD and BNB Examples: - Liquidity is in BNB or ETH : --> use LIQUIDITYINNATIVETOKEN = true / USECUSTOMBASEPAIR = false
- Liquidity is in BUSD --> use LIQUIDITYINNATIVETOKEN = false / USECUSTOMBASEPAIR = true / BASEADDRESS = 0xe9e7cea3dedca5984780bafc599bd69add087d56
Last updated
