Ethereum, BSC & Base
Last updated
Last updated
The image below shows the Auto Snipe Configuration Menu on Ethereum. BSC and Base will have similar menus with some differences that will be highlighted throughout this page.
Before we go through the configuration options, we point out a few important things:
On Ethereum, Block-0 snipes from all Maestro users are gathered in one big bundle, and tips or bribes are offered to the blockbuilder through Block-0 Tipping in exchange for having the bundle placed right after the launch or target transaction. In this case, you will also have the option to initiate a backup transaction for your auto-snipe to guarantee an entry in case the bundle doesn't go through. When Auto Snipe is targeting a Block 1+ snipe, either due to deadblocks detection or due to a private launch, auto-snipes transactions will be sent individually, and without any tipping or bribing since there's effectively no launch or target transaction. In this case, no backup transactions will be sent as there's no risk of having the bundle rejected. Finally, it is important to note that if the token launched, but Auto Snipe is waiting for a transaction that lowers the Buy and/or Sell Tax to your set limits, then it will be considered a Block-0 snipe. In other terms, your transaction will be part of a bundle and tips or bribes will be offered to the blockbuilder in exchange for having the bundle placed right after the tax-lowering transaction. If you have the option enabled, a backup transaction will also be sent to guarantee you an entry should the bundle fail to go through.
For BSC, there's no concept of bundling or tipping, and by extension, no backup transactions. Auto Snipe will initiate your auto-snipe as soon as it is safe to do so, while considering deadblocks, and tax limits. Consequently, you could end up sniping in Block-0 or Block-1+ depending on the case.
For Base, there's no mempool where we can monitor launch transactions, and hence, Block-0 sniping is not possible. By extension, the concept of bundling, tipping and sending backup transactions doesn't apply here. Auto Snipe will watch for the launch or target transaction on the mined side, and will initiate your auto-snipe as soon as it is safe to do so, while considering deadblocks, and tax limits.
Now that we've laid out how Auto Snipe works on each of Ethereum, BSC and Base, we turn our attention to the options of the Auto Snipe Configuration:
Exclusive to Ethereum
Choose the slippage to be used for your auto-snipe and for your Backup Transaction when you have the option enabled (Exclusive to Ethereum).
If enabled, Auto Snipe will ONLY trigger your auto-snipe if you can afford max TX at the time. If not, then your auto-snipe will be deactivated. This is particularly useful if you're interested in getting max Tx or nothing.
Exclusive to Ethereum and BSC
This setting should be enabled if you are ONLY looking for a Block-0 snipe. In other terms, if Auto Snipe is set to trigger on Block-1+ either due to deadblock detections or due to a private launch, then your auto-snipe will not trigger. Please note that if Auto Snipe is waiting for a transaction in mempool that lowers taxes to your set thresholds, then this is considered a Block-0 snipe and your auto-snipe will be triggered normally, even with Block-0 Only is enabled. However, if the tax lowering transaction was sent privately, your auto-snipe would not trigger since this qualifies as a Block-1+ snipe.
If you instead wish to completely halt the snipe when the launch taxes are not within your set thresholds, you should use Skip High Tax Launch which is detailed below.
If enabled and the buy and/or sell tax of the token at launch did not satisfy your set limits, then Auto Snipe will deactivate your auto-snipe. In other terms, Auto Snipe won't wait for a transaction that lowers the buy and/or sell taxes to a value that is within your set limits.
Through ⚡️Buy Tax and ⚡️Sell Tax, you can set the maximum buy and sell tax that you're willing to accept for your auto-snipe to trigger. If, at launch, the buy and/or sell tax of the token don't satisfy your threshold, Auto Snipe will wait for a transaction that lowers the taxes to an acceptable value and then trigger your auto-snipe. Specifically on Ethereum, this is paired with bundling your auto-snipe to the tax lowering transaction along with Block-0 Tipping. This is considered a Block-0 snipe where tipping or bribing is provided to the blockbuilder, and a Backup Transaction is simultaneously sent if you have the option enabled.
By default, both ⚡️Buy Tax and ⚡️Sell Tax are set to 50%.
Exclusive to Ethereum
As mentioned previously, Block-0 snipes on Ethereum can be paired with a simultaneous Backup Transaction to guarantee you an entry in case the main bundle fails to go through. This option is ONLY available for Block-0 snipes and hence can only be enabled when Block-0 Tip is also enabled. Backup Transactions can only be mined if the main bundle fails, and could still catch Block-0 if your Gas Delta is sufficiently high.
For ETH, this will be the gas delta used for Block 1+ snipes and for backup transactions. As mentioned earlier, Block-0 snipes will use tipping or bribing and their gas delta will be defaulted to 0.1 gwei.
For BSC, this will be the gas price used for all snipes, whether Block-0 or Block-1+. For Block-0 snipes, the bot will automatically ensure that your gas price is not above the gas price of the launch transaction to avoid frontrunning it. As mentioned earlier, there's no bundling, tipping nor backup transactions on BSC.
For Base, this will be the gas delta used for all Block 1+ snipes since Block-0 snipes are not possible. Similarly to BSC, there's no bundling, tipping nor backup transactions on Base.
This is the amount of ETH that will be tipped or bribed to the blockbuilder. Use values above 0.05 ETH to guarantee good entries. This will make the bundle more powerful against competing ones. As a reminder, Block-0 Tipping is not activated for Block 1+ snipes. More details on this advanced system can be found .
If enabled 🟢, the bot will automatically create the sell limit orders defined in "⚙️ Sell Limit" following an auto-snipe. If Auto Sell is disabled 🔴, no sell limit orders will be automatically added following an auto-snipe, even if you have them defined in "⚙️ Sell Limit". Initially, "⚙️ Sell Limit" will enherit the same limits defined in your , but you can further customize these limits directly from your Auto Snipe Configuration Menu. In such cases, the sell limits specified in the Auto Snipe Configuration Menu will take priority over the ones specified in your .
Now that you've set the default configuration, you can proceed to add, activate and further customize your auto-snipe, as detailed .
