Arbitrum
Last updated
Last updated
Figure 44 shows the Auto Snipe Settings of a random token on Arbitrum:
A quick summary on Liquidity and Method sniping is provided here.
We now go over the buttons of Figure 44.
This ⭐️Premium feature allows you to simulate contract launches directly through the bot. Our launch simulations will automatically identify deadblocks, launch taxes, launch methods, and the contract's max buy BEFORE launch. These parameters are extremely important to snipe safely when using Liquidity or Method sniping.
As detailed earlier, the values for Main, Multi and Slippage will mirror the ones specified in your Auto Snipe Configuration. However, you have the option to change these values directly in the Auto Snipe Settings (Figures 44) of the token.
Initially, the Liquidity and Method buttons will both be disabled and will have a red ❌. These buttons allow you to switch between sniping Liquidity and Method. For example, selecting Method transforms the four buttons below it into Method sniping options, while selecting Liquidity transforms said buttons to Liquidity sniping options as depicted in Figure 44. Clicking on these two buttons does NOT enable Auto Snipe, which is done by enabling Snipe Liquidity and Snipe Method as discussed later in this page.
If you press on Liquidity or Method, you can setup block delays for each type of snipe. If you know that the contract has some deadblocks right after liquidity is added or the chosen method is activated, you can set up a block delay to execute your snipe right after the deadblocks pass.
For each type of snipe (Liquidity or Method), you can either specify a native amount in ETH or the exact amount of tokens desired:
🎯 ETH Amount: Enter the native amount in ETH that you would liken to snipe. If you're sniping with 0 block delay (Block-0 snipe), make sure the set amount won't violate the contract's max buy as this will cause your transaction to fail.
🎯 Token Amount: Enter the exact token amount you would like to snipe. Alternatively, you could also specify a percentage of the total supply (example 1%), and the bot will automatically convert the percentage to an exact token amount. This is very useful if you want to secure a max buy/wallet on launch.
To enable Liquidity sniping, select Liquidity and then press on the corresponding Snipe Liquidity button to enable sniping of that type. If Snipe Liquidity is enabled (signified by a ✅), then the Liquidity button above will also display a ✅, as shown in Figure 44. With this set, the bot will attempt to buy immediately when liquidity is added to the token.
To enable Method sniping, select Method and then press on the corresponding Snipe Method button. The bot will then ask you for the ID of the method that you would like to snipe and will provide you with a list of Method IDs that it was able to identify for this contract. An example is shown below in Figure 45:
Every method in a contract contains an ID. When a wallet initiates a transaction to call a method on a contract, the transaction contains a 4-byte method ID. This is equivalent to 8 unique hex characters. For example, the method ‘enableTrading’ with no parameters is equivalent to ‘0x8a8c523c’.
If you cannot find the desired Method ID in the set of Method IDs provided by the bot, you can search for the required Method ID within a specific contract using the instructions in the Appendix.
After providing the Method ID, the Snipe Method button will be enabled (signified by a ✅), and the Method button above will also display a ✅. With this set, the bot will now attempt to buy immediately when the provided method is executed by the contract owner.
As mentioned previously, for Liquidity and Method sniping, the usage of Slippage will differ based on whether you're sniping with an exact native amount or an exact token amount. We go over these differences below:
Slippage for Exact Native Amount: In this case, you can select a slippage percentage ranging between 0% to 100%. This slippage represents your loss tolerance.
Slippage for Exact Token Amount: In this case, you can select use the Slippage field in two ways:
Percentage: Provide a percentage ranging between 0% and 1000%. When slippage is set to X00% and you attempt to snipe an exact token amount, the bot will detect the amount of ETH needed to buy that exact token amount, and then send (X+1) * the detected ETH amount to secure your buy. For example, you wish to auto-snipe exactly 100 tokens, and the bot detects that 100 tokens cost 0.1 ETH. If your slippage is set to 200%, the bot will send 0.3 ETH (3*0.1 ETH) to secure your buy. The router will then use whatever ETH amount it needs to get 100 tokens, and the remaining ETH will be sent back to your wallet.
ETH Amount: Alternatively, you can circumvent the bot's percentage-based estimations and set a strict ETH amount to be used. For example, you wish to auto-snipe exactly 100 tokens, and you're not willing to pay more than 0.2 ETH for these 100 tokens. You can then set the slippage to 0.2, and the bot will send 0.2 ETH and attempt to secure 100 tokens. The router will then use whatever ETH amount it needs to get 100 tokens, and any remaining ETH will be sent back to your wallet.
With this set, the bot is now ready to auto-snipe the token when the correct conditions are met.
Some final words on Liquidity and Method sniping:
Liquidity and Method sniping are meant for advanced users who can understand a bit of Solidity and navigate their way around a smart contract. You need to be able identify launch methods, deadblocks, and blacklisting mechanisms to maximize profits from these functionalities. The ⭐️ Premium exclusive Simulate feature can greatly assist in this matter.
In the rare case that a token has no liquidity and trade is gated by a launch method like “enableTrading”, and you’re not sure whether the owner will add liquidity then activate the method or the other way around, you can activate both Snipe Liquidity and Snipe Method in the Auto Snipe Settings of Figure 44, and the bot will be able to account for any order of transactions used by the owner.
