BSC BNB Pancake token sniper, buy, take profit and rug check
BSC BNB Pancake token sniper
The BSC token sniper listens for new blocks on BSC relating to the pancake swap factory contract. The createPair
log event is emitted on the pancake swap factory whenever a new liquidity pool is added. The sniper will filter the logs from these blocks to find these createPair
events. Then with the correct RUG checks it will buy the token, after a certain amount of profit has been made it will automatically sell the token.
This is a free project but any funding is appricated. ETH/BNB: 0x71f74dEbb7fd42E61de32256537284E06DE8812d
Telegram: https://t.me/joinchat/pW9TyMXOkx03Nzg0
The Config is listed in appsettings.json
There are values which you will have to set yourself, these are denoted with xxx
.
Inside the config you will see BscHttpApi
and BscNode
keys.
Both are obtained from https://moralis.io for free. You will have to navigate to Speedy Notes and click endpoints on the Bsc Network.
Remember BscNode
should be WS mainnet Endpoints and BscHttpApi
should be Http endpoints
If you want to run the project you can go to releases and a binary that will execute on your OS, or install Net5.0 then compile and run the application. You can use dotnet run BscTokenSniper
to do this.
There are specific checks involved that this sniper does when buying tokens. Some config values in appsettings.json inside SniperConfiguration
are used to influence the rug checks. You can disable the Rug checks by setting the RugCheckEnabled
to false. Be warned this is dangerous.
MinimumPercentageOfTokenInLiquidityPool
. A example of this is if you want the token ZZZ to have atleast 90 percent of its supply inside the liqudity pool you can set this value to 90.ContractRugCheckStrings
LiquidityPairAddress
) inside liquidity pool. The config key is called MinLiquidityAmount
.LiquidityPairAddress
addressThe Sniper automatically sells once a certain percentage of profit is made. This is defined in the config key ProfitPercentageMargin
Please read CONTRIBUTING.md for details on our code of conduct, and the process for submitting pull requests to us.
We use SemVer for versioning. For the versions available, see the tags on this repository.
See also the list of contributors who participated in this project.