DiabloArb — FAQ
Short answers to the questions people actually ask, for both ways of running the bot: diablo.bot (we host it, settings in the dashboard) and self-hosted (the same sender from this repository on your own server). Every config key is in USER_CONFIG.md; the full knowledge base is AI_GUIDE.md. State of 21 October 2026. Support: Discord · Telegram chat.
1. diablo.bot or self-hosted?
- Is the bot on GitHub the same as diablo.bot? Yes — the same
senderbuild (todaye96545b6fb69) and the same on-chain executor. diablo.bot runs it for you with our RPC and Geyser; self-hosted you bring your own. - What does it cost? 7% of the profit of each winning trade, taken on chain by the executor. Nothing on misses or losses, no subscription. You pay the network costs of your own transactions (fees, priority, tips — see AI_GUIDE §5).
- Which one should I pick? diablo.bot unless you already run Solana infrastructure (RPC, Geyser, sender keys). Self-hosting gives full control over RPC, landing services, keys and the server's IP.
- Where is my key? diablo.bot: the bot's own wallet, downloadable any time from the dashboard. Self-hosted: it never leaves your server.
2. Temporal
- Where do I put my Temporal UUID? diablo.bot: in the Temporal bundles block (Background · Temporal bundles) — the first stream's UUID field; each extra stream may have its own UUID (empty = the one above). The Temporal card in the senders list is the plain sender (
temporal_uuid); the bundles block uses the same key when its own is empty. Self-hosted:temporal_uuid, andtemporal_bundle_uuid/temporal_bundle_N_uuidfor separate bundle keys. - Temporal bundles vs the plain Temporal sender? Bundles: a bundle without profit is dropped whole — a miss costs nothing, the tip is paid only on a win. The plain sender: a miss lands as failed (
0x7 NoProfit) and costs fee + priority; the tip is still paid only on a win. Both: tip at least 0.001 SOL. - What does
403 Forbiddenfrom Temporal mean? Temporal does not let this key (or this server's IP) send. Only Temporal can change it — a new key or their support. Since 21 Oct 2026 Temporal answers403to bundles from many keys while still accepting plain transactions from the same keys. - Key or IP — how do I check myself? Send a broken bundle with your key from the bot's server:
curl -s -o /dev/null -w "%{http_code}\n" -X POST --data-binary 'x' "http://ams1.nozomi.temporal.xyz/api/sendBundle?c=YOUR_UUID"200/400— the server's IP is fine (a403on real bundles then means the key);403even here — the IP is blocked. The same command from another machine tells the two apart. A plain send uses/api/sendTransaction2. - The marks in the dashboard. Next to a stream's key: red key rejected — Temporal refused it (401/403) on half of its answers or more in 5 minutes; red key rejected · stream stopped — 20 refusals in a row, the bot stopped that stream (on diablo.bot its switch is also turned off); yellow limit used up — too many
429, raise "Every". No mark — the key works. Put in a new key and Save to turn a stopped stream back on. The same marks stand next to every sender in the senders list — Astralane, Jito, 0slot, NextBlock, Falcon and the rest (build8a7b1cf1e3fd, dashboard from 22 Oct 2026): a key the service refuses is shown, and stopped after 20 refusals in a row, the same way. 429 Too Many Requests? Temporal's limit is 5 requests a second per key per Temporal server. With all regions a stream sends one copy to each server, so keep a stream at no more than 5 bundles a second (Every ≥ 200 ms) or use more keys (extra streams).- Can I pick regions? Yes (build
e96545b6fb69):temporal_bundle_regions = ["ams", "fra", "lon"]andtemporal_bundle_N_regionsper stream; empty = all. On diablo.bot — the region marks under "all regions" on each stream. From diablo.bot's server ams, fra and lon answer in ≈8 ms, the US regions in 70–130 ms, sgp and tyo in 160–210 ms: the near ones usually carry almost all accepted bundles, the far ones mostly spend the key's limit. "one region in turn" (_all_endpoints = false) sends each bundle to one of the picked regions. - Nothing lands through Temporal bundles — broken? Usually not: a bundle lands only when it wins, so the wallet stays quiet for hours while "sent" grows. Check the marks above and the bot's status.
3. Dashboard numbers
- "landed" in the dashboard is less than Solscan shows. The landed · since … card counts from the bot's last start, and every Save restarts the bot. Solscan shows everything. For a fixed window use the net card's 1h / 24h / 7d / 30d buttons (counted from the chain).
- Net is positive but the balance went down. Rent sits in token and nonce accounts (section 4) — shown as
+X rentunder the balance; it comes back when the accounts are closed. - The bot stopped by itself.
no SOL for fees— SOL ran out (top up and Start).no sending lane is switched on— every lane is off, e.g. the only lanes were Temporal streams whose keys were refused: add a key or a sender, Save.
4. SOL, rent, token accounts and nonces
- Lots of token accounts / nonce accounts ate my SOL. It is rent, not a loss: ≈0.002 SOL per token account (one per coin the bot traded), ≈0.00145 SOL per durable nonce (hot modes keep 32, ≈0.046 SOL). It returns when an account is closed.
- Close idle token accounts / "Close after". With
auto_close_atas = true(dashboard: Limits → Close idle token accounts) empty accounts of coins not shot forauto_close_atas_idle_hourshours (dashboard: Close after, h; 24 by default, from 1) are closed and the rent comes back. On a small balance set 1–6. Accounts holding coins or WSOL/USDC/USDT are never closed. Right away: the dashboard's close ata now / close nonces buttons, or self-hosted./sender atas closeand./sender nonces close(stop the bot first for nonces). - "Keep SOL above" (
min_sol_amount): with auto-unwrap on, when SOL falls below it the WSOL is unwrapped so fees can be paid. Below a small reserve (≈0.006 SOL) the bot pauses sending until SOL is back. - Is there a spending limit? No. The bot runs until stopped; control cost with the thresholds, pace and lanes (section 8).
5. Ladder: "Starts at" and why nothing is sent
- What is "Starts at … SOL/min"? In ladder mode the bot measures how much the on-chain arbitrage bots earn on each coin right now. A lane joins only when a coin's earnings reach its Starts at (
hot_rpc_sol_per_min,hot_senders_sol_per_min,hot_jito_sol_per_min). Lower = more shots and more cost; higher = pickier. - My bot sends nothing for hours. In a quiet market no coin reaches the threshold: nothing is sent and nothing is paid — by design. The minute summary shows the top coins' SOL/min. At 0.1 SOL/min a lane may sleep for hours; most bots use 0.03 for RPC copies and 0.03–0.06 for paid senders. Also check the bot is running and has SOL.
- Flow (
mode = "flow") never waits: it shoots the top 2 coins all the time — more presence, constant cost. Markets works without Geyser and shoots the markets list in a loop.
6. Other senders: Helius, Diablo Sender, Harmonic
- Helius on diablo.bot? Hidden: Helius limits our shared server IP. If you need Helius, run self-hosted on a clean IP, or get a Helius project key (ask Helius for sender limits) and set
helius_api_key— with a key 50 requests a second per region instead of 1 per IP. - Diablo Sender / SWQoS. Built into diablo.bot at no extra charge. For your own server it is a separate paid service (diablosender.com).
- Do I need a Harmonic searcher whitelist? Not on diablo.bot — it works as is. Self-hosted: optional;
harmonic_bundle_public = truesends without a whitelisted key at lower limits (AI_GUIDE §13). - Which lanes cost nothing on a miss? Bundles: Temporal, Helius, Astralane, Jito bundles, Harmonic, and Jito with
jito_classic = true. Plain senders cost fee + priority on a landed miss; RPC copies and SWQoS land every time.
7. Self-hosted setup
- What do I need? A Linux x86_64 server (near Frankfurt/Amsterdam/New York is best), a read RPC (
rpc), RPCs that accept transactions (send_rpcs), a Yellowstone gRPC / Geyser endpoint for ladder and flow (geyser_endpoint,geyser_x_token), and keys of the senders you want (Temporal UUID, Astralane, Jito UUID optional…). Install and run: AI_GUIDE §2. Dry run first:DIABLO_SENDER_DRY=1 ./sender config.toml. - Proxies? Not supported: the bot sends directly from the server; a
proxykey is ignored. - Updates? A restart updates to the latest build;
DIABLO_SENDER_AUTO_UPDATE=0keeps the current one.
8. Settings presets
Starting points, not a promise of income — results change with the market, hour and keys. Derived from 52 diablo.bot bots with a week of history (14–21 Oct 2026): only aggregated values, no one's settings copied. Over that week the median bot made +0.04 SOL a day net and 29 of 52 were in profit; a quarter lost more than 0.04 SOL a day, a quarter made more than 0.24 SOL a day. What separated them: the thresholds and how many paid lanes run at once.
| Low balance | Safe (starter) | Balanced | Aggressive | |
|---|---|---|---|---|
| For | under ~1 SOL, learning | first week, small steady cost | most users after a week | large balance, accepts losing days |
| Mode | ladder | ladder | ladder | ladder (or flow) |
RPC copies (spam_rpc) | off | on | on | on |
| RPC Starts at | — | 0.05 SOL/min | 0.03 | 0.01–0.02 |
RPC Every (process_delay_ms) | — | 400 ms | 200–250 ms | 100 ms |
| Paid senders | none | none or 1 | 1–3 (e.g. Astralane, Jito, Temporal) | 1–2, low thresholds |
| Senders Starts at | — | 0.1 | 0.03–0.05 | 0.01–0.02 |
Senders pause (hot_sender_pause_ms) | — | 250 ms | 200 ms | 100–150 ms |
| Sender priority (min–max, lamports) | — | 100–1 000 | 100–1 000 | 100–5 000 |
Priority cap (hot_priority_cap) | — | 30 000 | 30 000–100 000 | 100 000 |
| Sender tips (min–max) | — | 0.001–0.01 SOL | 0.001–0.03 SOL | 0.001–0.03 SOL |
| Bundle lanes | 1–3 (Jito, Astralane, Temporal bundles) | 1–2 | 1–3 | optional |
| Bundle tips | 0.001–0.01 SOL | 0.001–0.01 | 0.001–0.03 | 0.001–0.03 |
| Temporal regions | ams, fra, lon | ams, fra, lon | ams, fra, lon | ams, fra, lon |
| Close after (h) | 2–6 | 12 | 12–24 | 24 |
| Keep SOL above | 0.05 | 0.1 | 0.1–0.2 | 0.2 |
| Minimum balance | 0.3 SOL | 0.5–1 SOL | 1–2 SOL | 3+ SOL |
| Typical cost a day | ≈0.1 SOL | 0.1–0.3 SOL | ≈0.3 SOL | 0.8–1.4 SOL |
| Risk | lowest: a miss costs nothing | low | medium | high |
What the week showed (median per bot a day; small groups, so read as tendencies):
- No RPC copies, bundles only (14 bots): 10 of 14 in profit, cost ≈0.11 SOL, net ≈+0.05 SOL — the cheapest way to stay positive, fewer wins.
- Ladder, senders at 0.06 SOL/min and higher (24 bots): about half in profit, net ≈0, cost ≈0.22 SOL.
- Ladder, senders at 0.02–0.06 (9 bots): 5 of 9 in profit, net ≈+0.23 SOL, cost ≈0.33 SOL.
- Ladder, senders below 0.02 (4 bots): 3 of 4 in profit, net ≈+0.25 SOL, cost ≈0.8 SOL — the biggest winners and the biggest losers of the week were in the low-threshold group.
- Four or more paid senders at once (5 bots): 2 of 5 in profit, net ≈−0.03 SOL, cost ≈0.87 SOL — more senders on the same coins mostly add cost.
- Temporal bundles: check the key marks first (section 2) — many keys are refused for bundles since 21 Oct 2026.
Change one thing at a time and compare a day or two on the net card's 24h/7d.
9. CopyTrade
CopyTrade on diablo.bot (Solana → Copytrade) copies the meme-coin trades of the wallets you pick, from the same wallet as your Arb bot. Setup, sources, entry and exit rules, limits, the 1% fee, wallet safety and troubleshooting: COPYTRADE.md.
10. Scalper
Scalper on diablo.bot (Solana → scalper) buys the bounce after a big sale knocks a pump.fun coin down and sells it seconds later, from the same wallet as your Arb bot. Strategies, the ML signal, exits, limits, the 1% fee and troubleshooting: SCALPER.md.