DLMM

Settings of this module are being set in swap_snipe_tasks.csv in tasks folder.

There is specific settings for Meteora DLMM, so adjust the config.json accordingly.

"solana_meteora_dlmm_settings":

"exact_token_amount":

Format - true/false

This setting changes the token a and token b input variables vice versa. Example given: Case 1 "exact_token_amount" - false, TOKEN A - USDC, TOKEN B - WENWENvqqNya429ubCdR81ZmD69brwQaaBYY6p3LCpk, AMOUNT - 1; it means that the bot will send 1 USDC and get the amount of TOKEN B, like a regular buy tx in any snipe module. Case 2 "exact_token_amount" - true, TOKEN A - USDC, TOKEN B - WENWENvqqNya429ubCdR81ZmD69brwQaaBYY6p3LCpk, AMOUNT - 1; it means that the bot will calculate the amount of TOKEN A that has to be sent to receive 1 TOKEN B. For this case, it is not as vivid as in the first one regarding the amount of token a needed to be held on the wallet.

^^^^ Very important setting for DLMM, make sure to understand how it works.

compounded_swap

Format - true/false

This setting is needed to buy over the forced bottleneck of max purchase on this DLMM contract of Meteora.

For instance, on the launch of token $WEN there was a bottleneck that you may get maximum 50M of token per tx, which made people think that in order to get more, you had to send multiple txes. With the setting input to TRUE, you will have to adjust the "number_of_instruction", which will compound the number of instructions per tx, which will bypass the limit of 50M(or any other amount that may be) of the token received.

"number_of_instruction" takes info from AMOUNT from swap task, so each instruction would have the amount of tokens from AMOUNT. If the number of instructions get over the limit of your balance of token A, the whole tx would fail!!!!! If total USDC used in instructions will be 50, and you have only 10 usdc, the whole tx would fail.

So, lets get into details. Example given: Case 1 "compounded_swap" - true, "number_of_instruction" - 8, TOKEN A - USDC, TOKEN B - WENWENvqqNya429ubCdR81ZmD69brwQaaBYY6p3LCpk, AMOUNT - 1. The tx would have 8 number of instructions with 1 TOKEN A(usdc).

Case 2: "compounded_swap" - false, "number_of_instruction" - 8, TOKEN A - USDC, TOKEN B - WENWENvqqNya429ubCdR81ZmD69brwQaaBYY6p3LCpk, AMOUNT - 1. The tx would be just regular one, with only 1 instruction as the "compounded_swap" - false.

MODULE

meteora

TASKS

Default number is 1. This setting will make your bot multiply the tx flow based on the DELAY which is one of the next settings in this configuration file. Basically, this multiplies the number of txes sent every DELAY.

Example given: TASKS 1; DELAY - 100 = 1000/100 * 1 = 10 tx / sec flow. TASKS 2; DELAY - 100 = 1000/100 * 2 = 20 tx / sec flow.

TOKEN A (FROM)

Here you input the token address of the token you would want to swap with. The bot will use wsol for swapping with solana. You cannot swap with regular solana with Cerberus.

There are aliases that you can use

SOL USDC USDT You can just input these in this graph, the bot will understand what kind of tokens you wanted to use.

THE BOT USES WSOL WHEN SWAPPING WITH SOLANA.

MAKE SURE TO HAVE BOTH SOLANA AND WRAPPED SOLANA FOR FEES AND SWAP.

TOKEN B (TO)

Here you input the token address of the token you would want to swap to AND THE POOL YOU WISH TO SWAP IN

PAY ATTENTION TO THE JPEG AT THE START OF THIS SECTION, THERE IS DIFFERENCE BETWEEN POOL ID AND TOKEN ID

This graph should include SPL address of the token AND the pool address you want to run.

Example given: WENWENvqqNya429ubCdR81ZmD69brwQaaBYY6p3LCpk:66A2vg4jwC9oSp5MGikzefgibdC5oSS3oARKjGbd2R1L

pool id takes from the url, as shown on the screenshot.

means the bot will buy token WENWENvqqNya429ubCdR81ZmD69brwQaaBYY6p3LCpk in the pool 66A2vg4jwC9oSp5MGikzefgibdC5oSS3oARKjGbd2R1L

WALLET

Wallet name from solana_wallets.csv

SLIPPAGE

For this module it is static - 0

TX AMOUNT

May have double variable separated with ":" First variable is for purchase, second is for selling

This is the number of txes sent by the bot to buy/sell the token

Ranges between -1 to any number

-1 starts the infinite tx flow that stops after spotting the successful purchase

Example given: -1:10 means the bot will send infinite amount txes for purchase, and 10 for selling 5:5 means the bot will send 5 buy txes and 5 sell txes 5:-1 means the bot will send 5 buy txes and infinite sell txes until it spots the sell is gone through

AUTO SELL % (IF TP SL TP%:SL%)

Leave blank

Leave blank

AMOUNT

REFER TO exact_token_amount settings to understand how it works here!

This is the amount of TOKEN A that will be used in swap

IMPORTANT EXAMPLE Case 1 "exact_token_amount" - false, TOKEN A - USDC, TOKEN B - WENWENvqqNya429ubCdR81ZmD69brwQaaBYY6p3LCpk, AMOUNT - 1; it means that the bot will send 1 USDC and get the amount of TOKEN B, like a regular buy tx in any snipe module. Case 2 "exact_token_amount" - true, TOKEN A - USDC, TOKEN B - WENWENvqqNya429ubCdR81ZmD69brwQaaBYY6p3LCpk, AMOUNT - 1; it means that the bot will calculate the amount of TOKEN A that has to be sent to receive 1 TOKEN B. For this case, it is not as vivid as in the first one regarding the amount of token a needed to be held on the wallet.

RPC

Rpc name that will be used in this task from rpc.csv

You also can use multiple rpcs for 1 task row ( example: rpc1,rpc2)

TIMESTAMP

For this module it is specific

May have double variable separated with ":"First variable sets the START TX FLOW and second one is STOP TX FLOW if TX AMOUNT is -1:-1

Format - unixtimestamp (https://www.unixtimestamp.com/)

Example given: If set to 1706518800:1706518802, this means the bot will start sending txes at Mon Jan 29 2024 09:00:00 and stop at Mon Jan 29 2024 09:00:02

DELAY

This is the main setting for setting the tx flow.

Format is - milliseconds

Formula is = 100 delay = 10 tx per sec (1000/100 = 10) Example given: If set to 5, the bot will send 200 txes per second(if tasks 1)

SPEEDUP FEE

You can add a Extra fee to txes, FEE IN SOLANA Example given: if set to 0.00001, the txes would have extra 0.00001 sol fee if set to BLANK, no fee will be added

These fees are needed to compete with other botters inside a single block.