Giter Club home page Giter Club logo

bsctokensniper's Introduction

TELEGRAM GROUP: https://t.me/joinchat/LivGs7b26iBkNWE0 - please join to assist in development, ask questions, share any successes etc.

BSCTokenSniper v1.3 in development and will be released in next few days.

BSCTokenSniper v1.3 Beta - this still has bugs in it but should mostly work

This version still needs changes and improvements in it, it is still unfinished. More documentation coming shortly

Improvements:

  • Can queue a token if 2 are detected (rare but can happen)

  • PCS factory address now editable from config.json

  • detects if pancakeswaprouteraddress is in code more accurately (previously would ignore if text was different upper or lower case from config file)

  • Users are now warned if config.json file is incorrectly configured and program exits.

  • program automatically detects whether os is windows or not and applies appropriate title code (same script should work universally on any os with python)

  • rugdoc API integrated. This will reject tokens that are dodgy, have high fees (over 10%) and honeypots.

  • antibot delay implemented. This allows you to delay purchase for x amount of seconds specified in config file, as some bots will have a very high tax in the first few blocks

  • prevents tokens being bought that are same as previous

  • autosell feature now working (STILL GOT ISSUES WITH IT - SOMETIMES GIVES ERRORS)

  • some bits of code tidied up

BSCTokenSniper v1.2

Improvements:

  • Added code blacklist (code_exceptions.txt): the program will ignore any program with code that is in this file

  • Added min liquidity checker (won't buy token unless it has certain amount of liquidity) - edit threshold in config.json

  • Fixed issue with buy - saying transaction failed when it was fine

  • Changed to websocketprovider instead of httpprovider - alot more reliable and also faster, should be less crashing as well

  • You can now change websocketprovider node in config.json instead of being in code

  • Some bits of code tidied up

(SpecifiedTokenSniper is not updated and still in v1.1 folder, will be integrated in main program and in GUI in future)

Also massive thanks to Christiaan Van AS, Muhammed Nurhaqqin and everyone else on Telegram for development and support with this project.

BSCTokenSniper v1.1

Just a few improvements, but largely untested. Would greatly appreciate if you could give me feedback. Thanks!

Improvements:

  • Added 'check for test' to ignore tokens which have 'test' in their name.

  • Added 'try' and 'catch' clauses for buy token and listenForTokens function to avoid exiting with error

  • Added function to detect WBNB pair in either pair 1 or pair 2 (currently only detects WBNB in pair 1 which potentially ignores alot of tokens)

  • Created 'SpecifiedTokenSniper' script - this allows you to snipe a specific token at launch as soon as it gains liquidity, if you know the token address. If you're lucky (like the refinable bot) you could make huge amounts of money.

  • You can now pick what liquidity pair address you would like. It is set to WBNB by default (recommended) but you can change to anything if you wish.

New config.json entries:

  • "checkForTest": choose whether "test" is in the token's name. Only enable if checkSourceCode is enabled. Recommended.

  • "liquidityPairAddress": Leave it unless you want to change the liquidity pair address.

BSCTokenSniper v1.0

A bot written in Python to automatically buy tokens on the Binance Smart Chain as soon as liquidity is provided.

BSCTokenSniper is a bot written in Python to detect new PairCreated events in the Binance Smart Chain (when a liquidity pair has been created) and buy the token. It is quite reliable and works well but it is the first version, so if you find any problems/improvements/suggestions please let me know by raising an issue.

Description

The aim of BSC Token Sniper is to buy new tokens with a specified amount of BNB, with the aim of the price rising Once the bot detects a PairCreated event, it is able to check the token (mini audit).

It can check if:

  • Source code is verified.
  • If valid PancakeSwap v2 router is being used
  • If a mint function exists
  • If it is a potential honeypot
  • PancakeSwap v1 router address is not being used.

The user can decide whether to enable the mini audit or turn it off (bear in mind you will likely be investing in a lot of scams if you don’t). Once the token has/hasn't been through a mini audit the bot will then attempt to buy X amount of tokens with the specified amount of BNB. The bot will buy the tokens directly through the Binance Smart Chain using the PancakeSwap v2 router and factory address, so it is much quicker than the PancakeSwap web interface.

By avoiding web interfaces & Metamask and directly with Ethereum & EVM Nodes you can snipe tokens faster than any of the web-based platforms. This allows tokens to be sniped almost instantly. During our testing we found the bot would typically be within the first 3 buy transactions of all tokens it finds. The bot buys the tokens using the user's wallet address and private key. This information is kept secure, is only stored locally on your computer, and is only ever used to buy tokens (look through the code to see for yourself).

The bot does not incur any additional fees, only fees are BSC network transaction fees and PancakeSwap fees.

Prerequisites

  • Python 3 or later installed
  • Node.js installed (easiest way) – Install windows version from https://nodejs.org/en/download/
  • Web3 installed (in windows command line type: pip install web3)
  • BscScan API key (completely free of charge, create an account on BscScan and generate a free API key)
  • BSC wallet address and private key
  • enough BNB in your wallet to snipe tokens.

Setup

Supported OS's

  1. Windows
  2. Linux
  3. Mac
  4. Android

INSTALLATION

Windows

  1. Download git Git
  2. Download python Python
  3. Clone the repo:
  • git clone https://github.com/BytePhoenixData/BSCTokenSniper.git
  1. Go to repo directory
  • run cd BSCTokenSniper
  1. Install Web3:
  • pip install web3

If you facing an error during the web3 installation, you may need the following microsoft visual studio build tool. use this link.

Linux User

Install package With sudo Debian / Ubuntu:

  1. install all dependency using command below.

apt install git && apt install python3-pip && pip install web3

  1. Clone repository and install web3

git clone https://github.com/BytePhoenixData/BSCTokenSniper.git && cd BSCTokenSniper && pip install web3

Fedora Linux / Centos

  1. install all dependency using command below.

dnf git && dnf install python3-pip && pip install web3

  1. Clone repository and install web3

git clone https://github.com/BytePhoenixData/BSCTokenSniper.git && cd BSCTokenSniper && pip install web3

Arch Linux

  1. install all dependency using command below.

pacman -S git && pacman -S install python3-pip && pip install web3

  1. Clone repository and install web3

git clone https://github.com/BytePhoenixData/BSCTokenSniper.git && cd BSCTokenSniper && pip install web3

  • If you all find the error try this bellow command and may fix your problem.

pip uninstall web3 && pip install web3

or

pip install -U web3

Android

  1. Install Termux Link
  2. Update

pkg update && pkg upgrade

  1. Install dependency

pkg install git python3 python3-pip

  1. Install web3

pip install web3

pip install -U web3

  1. Clone the repo using git

git clone https://github.com/BytePhoenixData/BSCTokenSniper.git && cd BSCTokenSniper

Note: You may find an error when installing web3 in android. You should install dependency needed by web3 manually using pip. The web3 version that work for this bot is web3 5.x.x if your web3 is 3.x.x the bot will not work.

Run python script

Assuming you are in BSCTokenSniper Directory. run python3 BSCTokenSniper.py To use other version you need to go to the directory needed and run the python script.

Configuration File

When you download the bot, you will find a config.json file. This is where you need to add the following data.

walletAddress: your BSC wallet address (e.g., Metamask) walletPrivateKey: your private key of your wallet address (your private key is kept safe and not shared in any other place) amountToSpendPerSnipe: The amount in BNB you want your wallet to spend on every new token. (e.g., 0.00025 means a new snipe will spend 0.00025 BNB on the new token) transactionRevertTimeSeconds: Time to spend before transaction reverts. Recommended to leave at default. gasAmount: amount of max gas to use per transaction. Recommended to leave at default. gasPrice: max price of gas to use per transaction. Recommended to leave at default. bscNode: Address for custom BSC node. Recommended to leave at default. bscScanAPIKey: Your API key from BscScan. liquidityPairAddress: Address for liquidity pairs. Recommended to leave at default. minLiquidityAmount: The minimum amount of liquidity in BNB in a token that the bot will purchase. The bot detects the amount of BNB in a newly detected token, and only buys tokens that have liquidity higher than the amount specified in the config file. Set to -1 to disable. observeOnly: enabling this will bypass the mini audit feature which allows you to observe how the bot audits tokens. Recommended to try this at the start to make sure the bot can scan for new tokens.

Mini audit

The bot has an optional mini audit feature which aims to filter some of the scam coins (eg. wrongly configured, honeypots). Obviously, this is not going to be as good as a proper audit (eg. CertiK) but at least the coins the bot will buy will be higher quality and if you enable the options, you should be able to sell the tokens later on (provided it hasn’t been rugged).

The following json entries are for mini audit. Set all to false to disable mini audits, although beware you will probably be buying a lot of scam coins. checkSourceCode: checks if source code is verified. This function is needed for all the other functions so if you disable this be sure to disable all the other audit options. Recommended. v1.3 onwards will use RugDoc tool to check for honeypots and high fee tokens.

checkValidPancakeV2: checks if the correct PancakeSwap v2 router address is used in the code. Be aware some contracts may externally set their router address so this function may reject a potentially good token. Not recommended.

checkMintFunction: checks if a mint function is present in the code. Recommended.

checkHoneypot: checks the code to see if it might be a honeypot (where you can buy tokens but cannot sell). Recommended.

checkPancakeV1Router: checks to see if the PancakeSwap v1 router address is used in the code. You will not be able to sell the tokens later on if PCS v1 router address is used. Highly recommended.

checkForTest: checks for tokens that are named 'test'. Often these tokens don't work or are not an investment opportunity.

Note: be very careful when editing config.json and make sure to not alter the syntax. For mini audit options, either use “True” or “False” making sure to capitalise the 1st letter. Any other spelling will not work.

Things to note

  • Do not worry if you are not seeing any new tokens being detected. There are often around 10-20 new tokens being created per minute but that can vary quite a lot. Sometimes no new tokens may be detected for a few minutes.

  • The bot only buys tokens whose liquidity is paired with Wrapped BNB (WBNB). You could alter the code to buy tokens paired with another currency if you wanted.

  • Please check that you have enough BNB in your wallet to afford sniping new tokens. If you don’t the bot will not work.

  • Please be careful when editing the config.json file. If you delete a comma or quotation mark etc. the bot will not work and throw an error.

  • To launch the bot, run the ‘launchBSCTokenSniper.bat’. The bot should then open in a cmd window and load.

  • Don’t left click in the cmd window as it will enable select mode and stop the output (you will see ‘Select’ in the title). If this happens right click your mouse to deselect it.

FAQs

I've sniped loads of coins - but how can I check which ones have made a profit?

  • For this go to poocoin.app, click 'Wallet' and connect your Web3 wallet that you are using for your bot (eg. Metamask).
  • It will then give you the list of tokens in your wallet and show you which ones have made the highest profit.
  • Click the descending arrow next to the balance tab to show highest to lowest tokens value.
  • Then you can manually sell the tokens which have made you a profit on PancakeSwap.

I keep getting ‘Transaction failed’ – what’s going on? Either:

  • Gas amount / price too low
  • Wallet address / private key incorrect
  • Not enough BNB to pay for the token and TX fees

The bot isn’t sniping that fast (eg. couple seconds between detection and buying)

  • This is mainly due to internet speed and computer processing power.

Risks:

Investing in BSC tokens / shitcoins is risky and be aware you could lose all your money. For this reason, do not invest more money than you are prepared to lose. It is pretty much impossible to snipe bots very early and be sure it isn’t a rug pull. When people create tokens in most situations, they will manually create liquidity in PancakeSwap. This is when the bot will detect the token. If they burn / lock liquidity, they will then usually send their LP tokens manually to a deadcoin address or put them in a liquidity locker. Therefore, you can’t immediately snipe the tokens with 100% certainty they aren’t rugpulls.

The mini audit feature can’t be 100% accurate but aims to filter out the majority of scams / hacks and reduce the chance of losing your money. If a programmer creates token code in a unique way, they may be able to bypass detection although this is generally quite rare, as the majority of tokens are forks of big projects with very little of the code having been changed e.g., Safemoon.

Things to do / improve / fix:

  • Look into rugpull detection (in development)

  • Auto sell after certain profit reached? (in development)

  • Make ETHTokenSniper that does the exact same but runs on the ethereum blockchain

  • Are all tokens that haven't verified their source code bad? Probably not. But the bot currently just assumes that developers will verify their source code before adding liquidity. The bot can't tell if it's a scam or not if the source code isn't verified.

  • Also maybe an option to sell it at a certain price point. Look what happened to Refinable, a bot bought a huge chunk of the tokens and made an insane amount of money in a few minutes.

  • Improve reliability: the program can sometimes unexpectedly freeze. This is being investigated.

  • Allow user to set slippage percentage

If you’ve found this bot useful and have profited from it please consider donating any token to my BSC wallet address: 0xE75470B9a7c93038195ca116E342c42F6B3F758b

Also consider donating to our other developers: 0x3a5A12dfffD327AFdaC7BEA60ECF7A48410E873a (Christian Van AS)

bsctokensniper's People

Contributors

bytephoenixcoding avatar fabifighter007 avatar gcvanasel avatar geeks121 avatar

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.