Recommended Setups
Sniping a specific token
If you have the early token address, also known as ca (contract address), I would suggest to run a mix of setups to increase your chances of sniping the token as soon as possible. Since only one buy transaction will ever succeed, running a mix of setups is the best way to guarantee a token will be bought as early as possible.
My recommendation is to setup different bot folders and run instances in parallel with different setups to ensure better success rate.
Default/Jito mode + Pre Spam Openbook
If you want to snipe this token under all circumstances, running pre spam mode can help very much. As detailed here this mode will snipe for pools where the market has been created in Openbook, but it hasn't been detected yet in Raydium. This means you are sending buy transactions before the pool even exists, which can greatly help to get early block buys.
Default
I would run a high Buy TxAmount here, like 18,000 with a Tx Delay of 0.2 seconds. Which would basically spam the pool for 1 hour, with a rate of 5 buy transactions per second. As mentioned before, sending this many buy transactions will drain your SOL wallet in fees, but this is the best way to spam send transactions and get an early block buy. With this mode I have personally been able to buy in 1st block after pool initialization many times.
Jito
The advantage of running this mode is that you will not be charged for failed transactions, as Jito ensures only successful transactions are forwarded.
At the time of writing this document, Jito has an RPC rate limit of 5 requests per second. This means, at maximum we should not be having a Tx Delay below of 0.2 seconds, in order to avoid being rate-limited. As for Buy TxAmount , I would do a high value, as we will not be charged for failed transactions, so we can be pre-spamming this pool for a long period of time with no consequences.
Note: In both cases, if the bot has detected you bought tokens, it will stop sending buy transactions.
In the case we want to auto sell the tokens as soon as bought, you should enter a value of 0 for Auto Sell Delay (seconds) , and sell transactions will also be sent in parallel of the buy transactions, using your Sell TxAmount and Tx Delay values. If you don't want to auto sell tokens as soon as bought, you should leave the value for Auto Sell Delay (seconds) blank/empty.
Pros:
Very effective method to get buys in the first blocks.
Since you are not waiting for the pool to load, you are not depending on your RPC to give you a fast update on the new pools, which always introduces a delay when sniping a token.
Cons:
Some markets load minutes, hours or days earlier than when the pools have been loaded. This means that since it is impossible to know when/if a pool will be released which matches your token address, it's hard to know for how long we want to run pre-spamming, and consequently draining SOL fees.
Liquidity for the pool is unknown when running pre spam since the pool is also unknown. This means your minimum liquidity values will be ignored here.
Default/Jito + No Pre Spam Openbook
This method relies on how fast your RPC/Jito client updates pool information to the bot. As soon as a response has been detected, the Raydium pool is live.
Default
This mode will send buy transactions as soon as the pool has been detected to go live through your RPC's websocket. Ideally you want to enter here a high Buy TxAmount like 200 or 300, to try to forward as many buy transactions as fast as possible, since the pool is already live.
Jito
With this mode, buy transactions will be sent through Jito validators, as previously mentioned they only constitute for 30-40% of the Solana network, therefore if the first blocks belong to the Jito validator network, and you have a high enough Jito Tip you can guarantee first block buys as long as you have a fast server. On the case where the first blocks don't belong to Jito, then you are likely sending the buy transaction on later blocks. Since Jito has a 5 req/second limit, I suggest to have a Buy TxAmount of 5 at best.
Moreover, you must provide a high enough Jito Tip so that your transaction is included onto the Jito validator, and it must be the best tip from all the others sending bundles for this same pool.
To help ensure your success rate at sniping with this mode you can follow official Jito's recommendations, and if you own several Minter Suite licences, you should run them in servers distributed across different geographical locations which are close to Jito servers.
In the general case, if you want to start selling as soon as possible, you should use an Auto Sell Delay (seconds) value of 0. Auto Sell Profit Margin and Auto Sell Stop Loss will also be considered for selling if they are not 0 too.
Pros:
Liquidity values for the pool are known, so you can properly filter out pools which don't have your wanted minimum liquidities.
You are saving draining fees as transactions will only ever be sent when the pool is known to exist and live.
Cons:
In the case for default/jito mode, you 100% rely on your server and RPC speed to get early block buys. The slower they are, the later your buy transactions will be submitted and processed.
Sniping in AFK mode
When running with afk mode, that is when you have set the value afk into Token Out field, you are basically running for all new pools which match your minimum liquidity criteria and abused pool criteria. On such cases you want to mainly be running two sort of setups:
Default/Jito mode + Pre spam Openbook. The only thing I would change here is the
Buy TxAmountas it can get very spammy very fast forDefaultmode. I would take into account that you are sending all those buy and sell transactions for every new pool detected, so you probably want to reduce that number to avoid being SOL drained in fees.
Last updated