Bot configurations
This is an example config.toml file.
Routing
In routing, you define which mint(X), a raydium pool that is SOL/X, a meteora dlmm pool that is SOL/X. The bot's onchain program will check if there's a profitable route between the two onchain, and find the optimal trade size, and execute the trades if there's any.
Currently the bot only support one raydium pool and one meteora dlmm pool for each list, you can define multiple different ones for the same mint/raydium pool and different meteora dlmm pool. A later version will alow using multiple meteora dlmm pool together.
mint_config_list
You can define multiple mint and pools. The bot will send out a tx, wait for process_delay ms, then send again and repeat for every mint you define.
You can also define more than 1 meteora dlmm pool. If you use more than 2 you need to add an address lookup table for it as well, otherwise the tx will be too big.
RPC
You just need to put your rpc's url here. This is NOT the rpc you use to send transactions.
Spam
You can set the rpc you use to send transactions. This can be the same as your reading rpc.
Jito
You can also enable sending through jito. Though the success rate of using jito is much lower due to the tip auction and how jito works, but the up side about it is you won't have any failed transactions.
Note: The bot currently only work with one ip, and if you have uuid you can use it with the bot as well. It doesn't support multiple ip rotation yet.
Note: The bot will send out tx through all the different urls one by one, instead of sending the same tx to all. This way you can have an effective 5/s rate limit with jito as this bot requires sending out a lot of tx.
Kamino flashloan
When enabled, you don't need a lot of wsol in your wallet.(You need some to keep your wsol account open). But this will add 73,000 compute unit to your tx.
Wallet
Last updated