Setting up an Auto Snipe

Interactive Guide

Additional information on sniping configurations and ETH-Specific configurations:

Simulation

The token is resimulated every single block, and the information gets updated automatically. Token name (Chain), Contract address, If your snipe is registered or not. Token Info: Buy | Sell taxes, Max transaction in % (if there is one), Deadblocks (will be set automatically), How many Sigma users are doing First or Fail on this token, (ETH mainnet only) Your active snipe settings, Useful links

Wallets and Gas

Specify the wallets you would like to snipe the token with: Pressing All button will select all of your wallets: Make sure to setup enough wallets before sniping! Select the amount of Gas you would like to use for your transactions: The more Gas you use, the better position in the block you will get (if FoF is not active), but the transaction will cost you more.

Slippage and Antirug

You can enter a custom Slippage value by pressing Slip: Slippage is calculated after taxes. For example, if you plan to buy a token with 1 ETH, and there's a 50% tax on the token, your initial 1 ETH will be reduced to 0.5 ETH due to the tax. Then, the slippage is applied. Consequently, the actual minimum amount you'll end up buying may be much less than 0.5 ETH. For tax protection you can select the maximum buy and sell taxes in the settings. Slippage is calculated not on token price fluctuation, but on the amount you are trying to buy. For example: You are trying to buy 1 Eth worth of Pepe and you have slippage set at 50%. This means that right after buying you are accepting that your tokens will be worth anywhere from 0.5 Eth to 1 Eth (if taxes are at 0%) Keep in mind, there is no anti-mev on Binance Smart Chain, so please use Slippage! On Ethereum, the AntiRug setting can be toggled on/off:

AntiRug is an all-in-one protection from all the things that are nasty - rugs, taxes, blacklists and everything in-between. You can enable/disable it by clicking this button: AntiRug will sell on high-impact sells, for example if dev dumps 10 wallets at once, the bot will frontrun these transactions. Red is disabled, green is enabled.

MaxTX and MinTokens

MaxTx enabled (green) - let’s say the token has a max transaction of 1% and you select a buy amount of 0.3 ETH. If the 1% of the tokens supply is more expensive than 0.3 ETH, the transaction will fail. If the price is below 0.3 ETH, the transaction will succeed. MaxTx disabled (red) - let’s say the token has a max transaction of 1% and you select a buy amount of 0.3 ETH. If the 1% of the tokens supply is more expensive than 0.3 ETH, the transaction will still go through. You will buy tokens worth 0.3 ETH and the supply you buy will be less than 1%. MaxTx limits your risk when buying very volatile tokens. If the token does not have a maximum transaction amount set up, this feature will not be used. To enable MinTokens, click on the button and enter your desired supply %:

When MinTokens is enabled, the bot will try to buy the supply you entered or more for the Buy amount you selected. For example, your buy amount is 0.2 ETH and you wish to purchase at least 10% of the total supply for the 0.2 ETH. In this case, you will get 10% of the supply (or more), or your transaction will fail. Red is disabled, green is enabled.

FoF and Pre-Approve

FoF stands for First or Fail, meaning that if you don't get first position in the block, your transaction will fail.

Red is disabled, green is enabled. You will see how many fellow Sigma members are sniping the specific token using FoF at the top of the menu:

Clicking Pre-Approve sends out an approve transaction before the token goes live. By pre-approving your transaction before the token launches, you can sell your tokens one block faster, as the approval is already in place when the token becomes live. FoF and bundles are only available on Ethereum

Settings

To access the settings, click on the 🔧Settings button:

There are a few interesting settings that need some explanation:

Min Liquidity - if the token developer adds an amount lower than you specified to the liquidity pool, your transactions will not be sent. Transactions will be sent when the requirements are met. Amount is written in USD. For example, you have set Min Liquidity at 1000, and the developer adds 0.2 ETH to liquidity, in that case, your transactions will not be sent. Transactions will be sent when the requirements are met. Buy/Sell Tax - maximum amount of tax that your poor soul can tolerate. If buy/sell of a token is higher than your set amounts, your transactions will not be sent. Transactions will be sent when the requirements are met. For example, you have set Buy Tax at 10%, Sell Tax at 5%, the developer launches with 2% buy tax, which complies with your settings, and 7% sell tax, which is the reason why your transactions will not be sent. Transactions will be sent when the requirements are met. When Alpha mode is enabled (green) all of the security checks of the bot are DISABLED and you will NOT be protected from high taxes, honeypots, blacklists etc., etc. Red is disabled, green is enabled. Backup - Backup transaction in case your main one fails. That can happen if the developer decides to launch using Private transaction, or if the simulations sees some deadblocks. Backup transactions will help you get in in these cases. Backup transactions will use your Backup Mev gas amount (in settings), so don't forget to set it. Red is disabled, green is enabled. (available on ETH only)