Criteria
The measurable properties of a volume tool: custody, venue coverage, control surface, failure reporting and the questions that expose each one.
CRIHow to judge a Solana volume bot
This desk does not publish a leaderboard. It publishes the criteria, the class comparisons and the test protocol that let you judge a volume tool yourself, including the ones we have never heard of.
We name no winners, publish no vendor scores and accept no payment for coverage. Where a console appears in an example, it is labelled as a third-party product.
The screening sheet
- C1 Custody model verify
- C2 Venue coverage ask
- C3 Pricing structure verify
- C4 Control surface ask
- C5 Failure reporting test
- C6 Observability ask
Nine things a buyer can actually check
Feature lists are written by the seller. These nine properties can be verified, tested or forced into writing before money moves, which is why the whole site is organised around them.
C1Custody model
Whether the tool ever holds keys that can move your funds, and what the withdrawal path looks like if it does.
C2Venue coverage
Which Solana venues are actually routed, whether coverage is claimed or demonstrated, and how new venues are added.
C3Pricing structure
The full price expression: subscription, percentage, per-transaction fee, and every cost the quoted headline excludes.
C4Control surface
Which parameters you can set: wallet count, order size, spacing, venue selection, stop conditions and budget caps.
C5Failure reporting
Whether failed transactions are shown, counted and charged for, and whether you can reconcile them against the chain.
C6Observability
What you can see while a run is live, what you can export afterwards, and whether signatures are exposed at all.
C7Support behaviour
Response time before payment versus after, the channel of record, and whether answers are specific or deflected.
C8Contract terms
Refund conditions, cancellation, data retention and the paragraph that describes what happens when a run fails.
C9Operational maturity
Change logs, status history, incident disclosure and any evidence that the operator has run this longer than a few weeks.
Evaluations in depth
Four pieces that carry most of the method: the selection sequence, the scoring sheet, the custody question and the way pricing structures behave once a run is real.
How to choose a Solana volume bot
A five-stage selection method that starts with your own requirement rather than a feature list, and ends with a small paid test instead of a leap of faith.
Criteria 01The nine evaluation criteria
Nine properties you can actually check before paying, each with a scoring band, the evidence that satisfies it, and the answer that should end the conversation.
Criteria 02Custodial vs non-custodial
Who holds the keys is the single largest structural difference between two tools that look identical in a screenshot. A custody model matrix and the questions that reveal it.
Criteria 03Pricing models compared
Flat subscription, percentage of routed volume, per-transaction fee, credit packs and revenue share, each modelled against the same illustrative run.
Comparisons 04Three sections, three jobs
Criteria tell you what to measure. Comparisons tell you how classes of tool differ. The buying guide covers everything between shortlisting and paying.
Comparisons
Class-level comparisons rather than product rankings. Pricing structures, interface models and hosting models, each with the trade-off it hides.
COMBuying guide
What to do between shortlisting and paying: size a first budget, run a controlled test, and check the warning signs that predate most complaints.
BUYBefore the money moves
The three practical pages. Read them in this order if you already have a shortlist and a deadline.
Running a small controlled test
A repeatable protocol for a first paid run: what to fix, what to vary, which records to keep, and the pass conditions to write down before you start.
Open the guideRed flags before you pay
Fourteen warning signs grouped by severity, from marketing language that promises outcomes to support behaviour that predicts how a dispute will go.
Open the guideWhat budget a run needs
The cost stack of a volume run line by line, an illustrative worksheet you can copy, and the floor below which a run cannot produce a readable result.
Open the guideTesting one yourself
Most of what matters about a volume tool only becomes visible once a run is live: whether failed transactions are reported, whether the parameters you were shown are the parameters that apply, and whether the records you can export reconcile against the chain. A working console is where you check that. The one used in our examples is a third-party product that routes across Solana venues and exposes its own configuration surface.
Open a live consoleOpens in a new tab. We take no payment for the reference, receive no share of what you spend, and treat a functioning interface as evidence of nothing except that the interface functions.
How this desk evaluates
Three things worth knowing before you trust anything here.
The method
We evaluate classes of tool, not individual products. A criterion earns its place only if a buyer can check it before paying, or falsify it with a small test afterwards. Everything else is opinion dressed as analysis.
Where arithmetic appears, the assumptions are stated in the same block and the result is labelled illustrative.
Conflicts of interest
No vendor pays for coverage, placement or a favourable line. One third-party console is referenced in examples and in the header button, and it is disclosed on every page it appears on.
We do not accept product submissions for review, because a review we cannot verify is worth nothing to you.
What we will not do
No rankings. No star ratings. No aggregate scores for named vendors. No claimed win rates, no screenshots presented as results, no numbers we did not compute ourselves from stated assumptions.
The full policy, including how corrections are handled, is in the editorial policy.