Counter anti-bot measures
Be careful ! Antibot protections cannot be bypassed. But we have implemented many parameters to avoid them.
BUYAFTER_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 Chainsniper 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)
WAIT_FOR_OPEN_TRADE This option is for tokens where 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 enable this option, 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.
The bot can detect EnableTrading in 2 ways :
1. The bot scans pending transactions, and detect the 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: 1. "WAIT_FOR_OPEN_TRADE": "true_after_buy_tx_failed" --> but bot will try to make a BUY order as soon as he sees liquidity, and if Tx fails, it will launch wait_for_open_trade. With this option, bot will scan pending transactions and wait for the price to move AT THE SAME TIME
If he detects an openTrading Tx, or see the price move, he will BUY.
Examples of Tx : openTrading / enableTrading / tradingStatus / etc.
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.
2. "WAIT_FOR_OPEN_TRADE": "true" --> same as before, but bot won't even try to make a Tx after it detected liquidity. Bot will scan pending transactions and wait for the price to move AT THE SAME TIME
3. "WAIT_FOR_OPEN_TRADE": "mempool" --> same as before, but bot will only scan pending transactions (he will not check if price moves)
4. "WAIT_FOR_OPEN_TRADE": "mempool_after_buy_tx_failed" -> same as "mempool", but bot will try to make a BUY order as soon as he sees liquidity, and launch wait_for_open_trade if the Tx is failed
- Liquidity is in BUSD --> use LIQUIDITYINNATIVETOKEN = false / USECUSTOMBASEPAIR = true / BASEADDRESS = 0xe9e7cea3dedca5984780bafc599bd69add087d56
BUY/SELL TAX checker / Honeypot detector Coming soon :) stay tuned...
Last updated