SolanaMevBotUsing an AI Assistant
Set up and troubleshoot SolanaMevBot with ChatGPT, Claude, or another AI assistant
An AI assistant can help you write a config and read logs, but it only knows what you give it. Without the documentation it tends to invent config fields, mistake normal failed trades for bugs, and suggest code changes the bot does not need. This page gives the assistant the documentation and a set of rules to follow.
1. Give the assistant the documentation
Every documentation page is also available as plain Markdown: add .mdx to its URL. Give your assistant these pages:
- Getting Started:
https://solanamevbot.com/docs/onchain-bot/getting-started.mdx - How It Works:
https://solanamevbot.com/docs/onchain-bot/how-it-works.mdx - Bot Configurations:
https://solanamevbot.com/docs/onchain-bot/bot-configurations.mdx - Config Examples:
https://solanamevbot.com/docs/onchain-bot/config-examples.mdx - Sending Vendor Examples:
https://solanamevbot.com/docs/onchain-bot/sending-vender-examples.mdx
If your assistant cannot open links, use Copy Markdown at the top of each page and paste the text into the chat. The menu next to it opens the page directly in ChatGPT, Claude, and other assistants.
2. Paste these rules
Start the conversation with this prompt, then describe what you want to do:
I run SolanaMevBot version [the release I downloaded, e.g. 2.0.4].
Help me with it, and follow these rules in this conversation.
1. Use only the official documentation as your source:
solanamevbot.com/docs/onchain-bot/getting-started.mdx
solanamevbot.com/docs/onchain-bot/how-it-works.mdx
solanamevbot.com/docs/onchain-bot/bot-configurations.mdx
solanamevbot.com/docs/onchain-bot/config-examples.mdx
solanamevbot.com/docs/onchain-bot/sending-vender-examples.mdx
For the reference bot in rule 2, also use its README and
solanamevbot.com/docs/onchain-bot/onchain-program/v10.mdx
Never guess fields, defaults, or behavior; say you don't know.
2. Do not wrap, patch, or intercept the release binary. For a
feature it lacks, modify the open-source reference bot:
github.com/Cetipoo/solana-onchain-arbitrage-bot
3. Build the release bot's config.toml only from documented
fields. It rejects 1.x sections such as [spam] and [jito].
4. Check features marked "from 2.0.x" against my version above.
5. Change one setting at a time, and compare the logs.
6. A transaction that fails with "custom program error: 0x1"
found no profitable trade when it executed. That is normal.
7. Never ask for my private key, seed phrase, or
ENCRYPTED_PRIVATE_KEY file. Remind me to remove private keys,
API keys, Jito UUIDs, and keyed RPC URLs from configs and logs.Replace the bracket on the first line with the release you downloaded from the releases page. The bot does not print its version, so take it from the release archive's name.
3. Know what is normal
Most arbitrage attempts do not trade. Prices move between selecting a route and executing it, and the program refuses a trade that would not profit. Tell your assistant this before it tries to fix something that is not broken.
| What you see | What it means |
|---|---|
A transaction lands but fails with custom program error: 0x1 | No profitable trade at execution time. Transactions from json_rpc, submit_batch, and next_block senders still land and pay their network fees. See When there is no profitable trade. |
| A transaction succeeds but nothing was traded | The sender has no_failure_mode = true, which lets a no-trade transaction succeed and still pay its tip and fees. See Tips and no-failure mode. |
Bundles from jito, send_bundle, or harmonic never appear on-chain | A bundle that reverts does not land, so a bundle with no profitable trade leaves no transaction. |
| A signature is never found | The transaction was not included before its blockhash expired, even if an endpoint accepted it. That is not a bot error. |
| The feed is connected but the bot sends nothing | No route matches your [auto.sol] or [auto.usdc] filters. Lower min_total_profit or min_tx_count, or raise lookback_secs. See Automatic market selection. |
| Rate-limit errors from a sender | Set that sender's rate_limit_per_second to what your plan allows. The bot pauses a sender for two seconds after a rate-limit reply. |
4. Build custom features
The release binary is closed source. A wrapper or patch around it cannot add features, and one that changes or resends its transactions breaks it. When you need something the release does not do, start from the open-source reference bot instead. It is MIT-licensed Rust that calls the same onchain program with the V10 instruction, so you and your assistant can change it however you like.
Before you start:
- It is a reference implementation, not the release bot. You list pools by hand in
[[transactions]], it sends only through RPC endpoints, and it has no automatic market selection. - Its
config.tomlhas a different format, documented in its README. Do not copy fields between the two bots' configs. - The program charges the same fee whichever bot calls it: 10% of the profit above the transaction's
minimum_profit, paid in its settlement token, SOL or USDC (see Fees). A transaction that does not trade pays no program fee. The reference bot'sadditional_feeis a separate, optional share paid to a collector you set. - Every transaction it sends pays network fees, even when it finds no profit. Start with one
[[transactions]]entry and a longerprocess_delay_ms. - Give your assistant the repository's README and the V10 instruction page:
https://solanamevbot.com/docs/onchain-bot/onchain-program/v10.mdx
5. Ask for help
If you are still stuck, ask in the SolanaMevBot Discord. Include:
- the bot version you run;
- your
config.toml, with private keys, API keys, Jito UUIDs, and keyed RPC URLs removed; - the first 50 or so log lines after starting the bot, and any error lines;
- the signature of a failed transaction, if you have one.
Never share your private key, seed phrase, or ENCRYPTED_PRIVATE_KEY file with anyone, including an AI assistant or someone offering help. The SolanaMevBot team will never ask for them.