Ethereum, BSC & Base
Last updated
Last updated
Figure 37 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 options in Figure 37, we point out a few important things:
On Ethereum, Nitro 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 Nitro 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 Nitro 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. Nitro 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. Nitro 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 Nitro works on each of Ethereum, BSC and Base, we turn our attention to the options of Figure 37:
Click on this to cycle through your wallets. The selected wallet will be used as default for auto-snipes. If you want to have simultaneous auto-snipes with multiple wallets, you need to keep this setting set to your "Main" wallet as choosing any wallet other than "Main" effectively disables this functionality. This is discussed in detail in Section 7.
Can be used to enable simultaneous auto-snipes with multiple wallets. As discussed in Section 7, Auto Snipe is the only instance where initiating multi-wallet buys doesn’t require enabling Multi in Multi-Wallets. For further details on how to set this up, refer to Section 7.
Enable (✅) , disable (❌), or revert to global (🌐) settings for Smart Slippage. This will only be used for the slippage settings of the Backup Transaction when you have the option enabled. As a reminder, Smart Slippage will always take precedence over Slippage, and configuration settings will override wallet or global settings. In other terms, enabling or disabling Smart Slippage in your configuration will override the slippage settings specified in your Wallet Buy Settings. If you leave it on 🌐, Backup Transactions will simply use the Smart Slippage settings specified in your Wallet Buy Settings.
Choose the slippage to be used for your Backup Transaction when you have the option enabled. By default, Slippage in Figure 37 will mirror the Slippage value specified in your Wallet Buy Settings, but you have the option to further customize it in the configuration. As mentioned above, Smart Slippage takes precedence over Slippage so make sure Smart Slippage is disabled if you mean to use a custom slippage value for your Backup Transactions.
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.
Initially, Gas Price and Gas Delta will mirror the values specified in your Wallet Buy Settings, but you have the option to further customize them directly it in the configuration. In such cases, the values specified in the configuration will take priority over the ones specified in your Wallet Buy Settings.
If you wish to participate in Block-0 Tipping, make sure to have Block-0 Tip enabled ✅ here. It is recommended to always keep this setting enabled as blockbuilder tipping or bribing will make the bundle more powerful against competing ones. As a reminder, Block-0 Tipping is not activated for Block 1+ snipes, so you may leave this setting enabled regardless of the auto-snipe's target block.
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. More details on this advanced system can be found here.
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.
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, Nitro 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%.
This setting should be enabled if you are ONLY looking for a Block-0 snipe. In other terms, if Nitro 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 Nitro 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 Nitro will deactivate your auto-snipe. In other terms, Nitro won't wait for a transaction that lowers the buy and/or sell taxes to a value that is within your set limits.
This sets the slippage for all Nitro auto-snipes, including Block-0 and Block-1+. As mentioned previously, only Ethereum has additional parameters for slippage (Slippage and Smart Slippage) to cater for the Backup Transaction settings.
It is important to note that the usage of Nitro Slippage will differ based on whether you snipe using exact ETH amount or exact token amount. This is further detailed here.
If enabled, Nitro 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.
For Auto Sell, enabling this will ensure that Auto Sell is enabled by default in the Trade Monitor that will be spawned after your auto-snipe. The latter will only hold true if Auto Sell is also enabled in your Wallet Sell Settings, otherwise, you'd have to enable Auto Sell manually through the Trade Monitor AFTER sniping. The values for Sell-Hi, Sell-Lo, Sell-Hi Amount and Sell-Lo Amount will mirror the ones that are set in your Wallet Sell Settings, but you have the option to further customize them in the configuration menu. In such cases, the values specified in the configuration will take priority over the ones specified in your Wallet Sell Settings. The same applies for Trailing sell, as it needs to be enabled in both locations to be active by default after the snipe.
Now that you've set the default configuration, you can proceed to add, activate and further customize your auto-snipe, as detailed here.
