How to use a Solana volume bot: complete walkthrough
Most guides to this jump straight to settings. That skips the two decisions that determine whether a campaign is worth running at all: what you are trying to achieve, and whether volume is the thing that achieves it. This walkthrough covers the whole sequence, from deciding whether to run one through to knowing when to stop, in the order the decisions actually arrive.
First, decide whether to run one at all
The honest test is what happens after. If a token has a community, a reason to exist, or something arriving that people will care about, activity brings eyes to it at the moment those things can convert. If it has none of those, the campaign is the entire story, and it ends when the spending does.
This is worth deciding before any settings, because it determines the budget. A campaign supporting a real launch is a marketing line item with a purpose. A campaign standing in for one is a cost with no mechanism behind it. The realistic limits are covered in is a volume bot safe.
What to prepare before starting
The mint address is the only identifier that matters. Ticker symbols are not unique and names can be duplicated; the mint address is definitive, and getting it from the token's own source rather than from a search result avoids the most common and most expensive mistake in this whole process.
Budget deserves a number rather than an intention, decided before anything is running. Under live conditions with a chart moving, "a bit more" is an easy decision to keep making, and campaigns that end when the money runs out rather than when the plan says so are the norm rather than the exception.
On custody: a campaign needs funds to trade with, but it does not need control of your main wallet. Anything asking for a seed phrase or private key is asking for more access than the task requires, which is covered in how volume bot scams work.
Setting a budget that reflects real costs
Across the whole network in our current window, 6.1% of transactions failed while still paying their fee, and DEX swaps fail considerably more often than that average. Any plan that assumes every transaction lands is understating its cost.
Three costs make up the total. Base and priority fees, paid per transaction attempt regardless of outcome. Service commission, which for us is a flat 2% set out on the pricing page. And the SOL that cycles through the trades themselves, which is largely recovered since buying and selling returns most of it, minus fees and price impact.
The calculator does this arithmetic against current measured rates rather than an assumed average, and the full breakdown of where each component goes is in the cost breakdown.
Configuring the campaign
Enter the mint address in the dashboard and the venue is resolved from on-chain state: which pool carries real depth at the current price, and which program it runs on. That determination is remade during the campaign rather than fixed at setup, so a token that graduates or whose liquidity moves is followed rather than left behind.
What remains for you is the shape of the activity:
- Trade size should be large enough to register and small enough to leave the price where it was. The reasoning is in volume bot trade size.
- Interval should vary rather than tick like a clock, since perfectly even spacing is recognisable at a glance.
- Wallet count determines how many distinct participants the activity appears to come from, covered in how many wallets you need.
- Slippage should come from how much the pair actually moves, not from a default, as set out in slippage settings.
A full reference for what each setting does and how they interact is in volume bot settings.
What to watch while it runs
A falling landing rate usually means slippage is too tight for current conditions, trade size has grown too large relative to depth, or the network is congested and priority fees are no longer competitive. All three are adjustable while running.
Organic activity is the harder signal and the more important one. Your own volume is guaranteed by definition and therefore tells you nothing about whether the campaign worked. Transactions from outside the fleet are the actual result, and if none appear after several hours of sustained activity, that is information worth acting on rather than spending through.
What else is worth measuring, and what to ignore, is in how to measure if it worked.
Stopping properly
The tail costs very little because it is the low-intensity part by definition, and it is the difference between a chart that looks like it had a moment and one that looks obviously scheduled.
Decide the stop condition before starting. "When the budget is gone" is a decision made by default, and it usually means the money ran out in the phase where it was buying least. Better conditions are a fixed duration, a target that has been reached, or the absence of organic activity after a set period.
What happens to a chart afterwards, and how to read the aftermath without fooling yourself, is in after a campaign ends.
The mistakes that cost most
Each has the same character: nothing appears to go wrong, the campaign runs, and the result is worse than the budget should have bought. The full list with the reasoning behind each is in mistakes that quietly waste your SOL.
The one worth repeating here is the accounting error underneath all of them. Count swaps that landed, not transactions sent. On a venue with a high failure rate those two numbers differ by a large factor, and only the first one produced anything. That is why we publish measured per-venue failure rates rather than a single cost per swap, and it is the whole reason to run a Solana volume bot on published numbers rather than quoted ones.