Current behavior
The config file allows for user configured values such as :
"AmountToSnipe": 0.0005,
"ProfitPercentageMargin": 20,
"SellSlippage": 0.5,
"HoneypotCheckAmount": 0.0000001,

Desired behavior
Allow the user to input a value X and a value Y, the bot will then pick a random amount that is in between X and Y for every contract such as :
"MinAmountToSnipe": 0.0005,
"MaxAmountToSnipe": 0.005,
"MinProfitPercentageMargin": 20,
"MaxProfitPercentageMargin": 25,
"MinSellSlippage": 0.5,
"MaxSellSlippage": 1.5,
"MinHoneypotCheckAmount": 0.0000001,
"MaxHoneypotCheckAmount": 0.0000019,

Background
The bot detects a new token, runs audits and one of those audits is that there isn't enough liquidity which means we can't buy.

If all other audits such as honeypot / rugcheck pass but liquidity fails, it can be a legit token that just hasn't added liquidity yet.

Request
Add a liquidity monitor:

• If the token passes other audit checks but only fails liquidity, monitor it.
• If it's a specific contract snipe - include liquidity monitoring
• When liquidity is added, proceed to run the audit again (if it's random contract) or just buy if it's a specific snipe contract
  This means we can still come back to a new token after liquidity is added

Background
In the appsettings.json, the user specifies the "PancakeswapRouterAddress" and "V1PancakeswapRouterAddress".

The bot runs a check on the contract source code to see if the contract mentions the router address and if it's a match or not to what we list out.

This is to prevent some rug pulls that happened at the start of the bot.

Problem
Some valid contracts do not specific the router address in their contract code. Some legit launches do, some legit launches don't.
As such, the bot may be failing valid potential buys

Request
Allow this "Check source code for PCS address" to be set by the user in appsettings.json so the user can enable or disable it.

Fail all

Implement ability to turn on honeypot check from rugdoc: https://rugdoc.io/honeypot/

This request is to:

• Add a database or log file that stores every contract that was not bought due to a fail in the audit. whether it is a rugcheck, honeypot fail etc
• Each time the bot finds a new contract, it compares data against the log file as part of it's audit

Rules

• Previous contract with same name was rugcheck/honeypot failed?
• Previous contract owner is the owner of this new found contract?
• X Y Z (whatever else we deem as good data to check on each contract)

This means the bot is learning from historical data to help with risk assessment of new contracts

Allow the user to enter max % tax on both Buy and Sell and to allow the user to enable or disable this check in appsettings.json.

If it's enabled:
Detect Buy and Sell Tax % (example using honeypot.is) , if it's above the user configured value inside appsettings.json, return false / fail.

• Ability to run a blank ETH complaint blockchain locally
• Ability to deploy the token to rug check onto the chain
• Ability to clone the liquidity pools of the token to rug check
• Check contract owner if any
• Find all values in token contract which modify state and execute with random values and check if buy and sell still work
• Forward time and check if buy and sell still work

This comes with no gas cost as everything is local. Essentially should be quicker then any API calls and should work multichain and most chains have local nodes.

It would be nice to have a configurable amount of seconds that will delay the bot in starting the "Buy" after a token passes rugcheck/honeypot check.

ie The bot finds a contract, it passes all the checks, then I want to implement a 10 second delay on purchasing so it doesn't look as much like a bot to the devs

• Project should be unit tested.

Currently has 0% coverage

Background
Sometimes we already know an upcoming contract that will launch and we will want to target this contract as soon as it's available.

Request
Implement an option to select Specific Token Snipe so when selected, the user can:

1. Enter in the contract address for a specific token
2. Customize all values such as the snipe amount , audits etc for a specific token (even if it's different than the standard snipe on random contracts
3. Allow the snipe amount to be a token value rather than a bnb value so we can max buy if we know the token amount

• for a whitelisted address we want to snipe - we can have custom amounts like this:
  "WhitelistedTokens": [
  "0x0000000000000000000000000000000000000000"
  ],
  "AmountToSnipe": 0.00051,
  "WhitelistedAmountToSnipe": 0.05,

edit: removed 2. Enter in the name (if they don't know the contract address yet the bot will buy all "New" contracts with this name)

Hello guys, with SniperService.cs modified by twilker and the •original repo files from JayArrowz the bot now approve but fails same to sell with this error Fail with error 'PancakeRouter: INSUFFICIENT_OUTPUT_AMOUNT€'
For sure caused by a low slippage. Is this possible to add the function for modify slippage sell?

Thanks for your work

•Original repo files i mean the latest files provided by JayArrowz

It will be a good idea if you can add a functionality that will blacklist old tokens that kees adding liquidity. Just as we have the whitelist functionality create a similar one for blacklist. With the blacklist functionality once we detect old tokens we can manually add them to the black list so that next time they add liquidity, the bot will ignore it and it will not waste any resources to perform a rug test on it. Remember we pay gas fees each time there is a honeypot test. Thanks

Hi, first of all thanks for sharing the code, I really appreciate the hard work involved in this project. I had a couple of questions regarding the algorithm since I am trying to make my own sniper but in Python.

I think one of the most critical parts of snipers is clearly the security and how fast you can check whether you are sniping a rug/honeypot or not. In this case, you have very well implemented a function that makes a small transaction to check whether the token is a honeypot, and if you can sell it then you proceed to buy the token as desired. Most of my questions are related to this part, I am interested to know:

1. How many milliseconds (or seconds) do you lose when you enable that safety check for honeypot?
2. Have you checked the profitability of the bot with and without the honeypot check? I guess adding the honeypot check sacrifices a bit on profit for more safety, but it is still better than manually doing the transaction on PancakeSwap.
3. In general, what is your experience on the profitability of this bot? Lets say, out of 100 sniped tokens, do you have any numbers on the amount of profit or loss?

Again, thanks for the code and looking forward hearing from you

Sometimes the profit % is calculated incorrectly causing the sell logic to not be hit.

Hi firstly great little project.

I am looking at this and getting a feel of how it hangs together and I though it would be great to load your own tokens and set profit targets and stop losses on them.

It seems new coins might be taking advantage of this or other bots to (presumably) allow initial rug-checks of small amounts but not any more or higher ones once more people are bought in. Not sure what sort of checks can be done, but perhaps waiting until you can read other sell outputs on the contract or perhaps adding a multi-buy/sell feature to follow the coin up so long as it's rising and sell-able?

Is this project no longer maintained?

This request is to allow wallet 1 + 2 + 3 configured in the json config file.

When a contract is found, only wallet 1 is used for the tests, such as the honeypot buy test.

If all of the checks are passed and the wallet is sniped, proceed to snipe it with each snipe amount allocated to wallet 1 , 2, 3 etc so we can multi buy in one flow without new instances running of the bot.

hi, I know which token I wanna buy, could you adjust so you can snipe that specific token?

• Ability to snipe on any ETH/BSC chain

When running in a docker container it would be great if we could override the appsettings configuration options with environmental variables. Configuration could then be specified in a .env file living outside the container.

Using .env in .NET

EnvironmentVariablesExtensions.AddEnvironmentVariables Method

Total supply not getting picked up correctly:

Total % in pool becomes too high due to this.