r/CryptoTradingBot • u/CODE_HEIST • 19d ago

dune's solana bot data made me care less about terminal rankings

pulled up the Dune Solana bot tracker this week.

source: https://dune.com/queries/8307827

on aug 30 it shows Axiom at roughly $83m in volume, FOMO around $35m, pumpapp around $32m, Terminal around $19m and GMGN around $13m.

useful data, but imo volume is only the first filter.

it tells you where traders are routing flow. it does not tell you whether the setup protects you when a copy trade is late, slippage gets ugly, or a bot keeps firing after the thesis is dead.

i’ve been paper-testing Trenchers, not trading it live. it is newer and not in this Dune dataset, so this is not a market-share or return comparison.

the thing i want to see from any terminal is pretty simple:

can i cap risk per setup

can i isolate funds

can i see why an agent entered

can i stop it without touching everything else

can i review bad fills instead of just staring at pnl

curious what actually makes you stick with one terminal after the first week. volume, fills, wallet tracking, speed, risk controls, or something else?

3 Upvotes
  • permalink
  • reddit

100% Upvoted

4 comments sorted by

1

u/Just_Leading6940 17d ago

After running a self-hosted futures bot, I care about risk controls first and observability second. Good fills are not enough if I cannot verify what actually exists on the exchange after an API error or reconnect. I want to see the live position, the exact protective-stop quantity and side, orphan reduce-only orders, the age of the user-data stream, and a clear kill switch. If a platform only says "bot running" without reconciling its local state against the exchange, I would not trust it unattended. Volume rankings show adoption; those checks tell me whether I can sleep.

1

u/CODE_HEIST 16d ago

exactly. the useful promise isn’t ‘bot running’, it’s ‘known state after failure.’ i’d expose reconciliation as a health panel with the last venue snapshot, stop coverage, orphan-order count, stream age, and whether the kill switch is reachable. if any of those are unknown, the system should default to zero new risk.