A Solana volume bot is software that funds a set of disposable Solana wallets and routes buy and sell orders through them against a specific token on a schedule, so that the token shows continuous trade flow instead of a flat line. Every order is an ordinary on-chain transaction. It moves the counters that boards sort on, which are volume, transaction count and the number of distinct makers. It does not create demand, it does not durably move the price, and it cannot produce holders.
Short version
- It is a visibility tool. The output is ranking inputs, not demand.
- It works anywhere a token trades: bonding curves, AMM pools, and across the migration between them.
- The cost is six lines, one of which comes back. Budget the venue swap fee, which most people forget.
- Spread and duration change the result more than the headline volume figure does.
- Solana is well suited to it structurally: sub cent fees and roughly 400ms slots make thousands of small orders practical.
Why Solana specifically
The technique exists on every chain and only really works on a few. A volume session is, by construction, a very large number of very small transactions, and that arithmetic is brutal on any chain with meaningful gas costs. A session of 2,500 orders on a chain charging a dollar per transaction costs more in fees than most launches are worth.
On Solana the base network fee is 0.000005 SOL per signature and slots land at roughly 400 milliseconds. Thousands of orders across thousands of addresses is a normal amount of activity rather than an expensive one, and the flow can be spread over hours without the fee stack dominating. The launchpad culture that grew on top of those properties is a consequence rather than a coincidence.
What it does on chain
The mechanic is simple enough to state in one paragraph. The engine derives fresh keypairs, funds each one with a small uneven amount of SOL, and then submits swap instructions against the token from those wallets with randomised sizes and randomised gaps. Each swap is a public transaction with a signature you can look up. The point is not concealment, which is impossible, it is that the aggregate should read as many participants rather than one.
Three counters move as a direct result: traded volume, transaction count and distinct maker count. On a bonding curve the venue charges its fee on each swap and the curve prices the trade mechanically. In an AMM pool the same thing happens against the pool reserves. Either way, buying and selling the same notional cycles the price up and back down while paying the venue on both legs, which is why routed flow is close to price neutral by design.
Where sessions run
| Venue type | Examples | What changes |
|---|---|---|
| Launchpad bonding curve | Pump.fun and similar launchpads | The curve prices every trade; progress toward graduation is itself a visible signal |
| AMM pool after graduation | PumpSwap, Raydium | Trades hit pool reserves; the token becomes eligible for pool-level trending boards |
| Across the migration | Curve into pool, mid session | Routing has to follow the token or the flow stops at the worst possible moment |
That third row is the one operators underestimate. Graduation is the moment a launch gets its widest audience, and a session that ends at the boundary hands the chart back to the market exactly then. The venue-specific detail for pools is in Raydium volume bot, and for curves in the Pump.fun volume bot guide.
What a session costs
| Line | Size | Comes back |
|---|---|---|
| Base network fee | 0.000005 SOL per signature | No |
| Priority fee | Set per compute unit, varies | No |
| Block engine tip | Optional | No |
| Token account rent | 0.00203928 SOL per new account | Yes, on close |
| Venue swap fee | Charged on every swap, both legs | No |
| Tool fee | Flat 1% of target volume | No |
The venue fee is the line that surprises people, because it scales with the routed notional and is charged twice on a round trip. Rent is the line that looks alarming and is not, because it is a deposit released when the token accounts close. Full worked numbers are in how much a volume bot costs.
The settings that matter
- Wallet count. Sets the maker count, which is a primary ranking input and the clearest tell when it is too low.
- Order band. The range order sizes are drawn from. A narrow band produces a metronome; a wide one produces a crowd.
- Duration. The single setting that changes how the tape reads, because it sets the gap between trades.
- Target volume. The headline number, and the least informative of the four on its own.
- Engagement layer. Comments and favourites, which address the one non-trading signal a tool can reach.
Operators tend to spend all their attention on the fourth item and none on the first three, which is the reverse of how much each one changes the outcome. The derivation of wallet count from volume and order size is worked through in how many wallets a volume bot needs.
The limits
No volume bot produces holders, because a wallet that cycles in and out of a position is not holding anything when the session ends. None of them move the price durably, because routed flow is circular. None of them can guarantee a trending slot, because the ranking belongs to a third party and depends on what everyone else is doing in the same hour. And none of them supply a reason for anyone to stay once they arrive.
PumpWave routes the volume you configure across the wallets you configure, for a flat 1% of target from 100 SOL up, with the fee shown before anything is funded and every trade verifiable while it runs. That is the complete claim. Whether the window is worth buying is answered honestly in do volume bots work.
Questions people actually ask
What is a Solana volume bot?
Software that funds a set of disposable Solana wallets and routes buy and sell orders through them against a token on a schedule, so the token shows continuous trade flow. It moves volume, transaction and maker counts, all of which are public and verifiable on chain.
Does it work on any SPL token?
A Solana volume bot works on any token that has a market to trade against, which in practice means a launchpad bonding curve or an AMM pool. A token with no liquidity anywhere has nothing to route flow through.
Is a Solana volume bot detectable?
The trades are public, so the question is whether the pattern is obvious. Identical sizes, trades on a metronome and wallets funded in one block from one source are all easy to read. Variance in size and spacing, and staggered funding, are what change that.
How long does a session take to set up?
Setup takes a few minutes. A session needs the token mint address, a size, a duration and a payment. There is nothing to install and no key to hand over.
Can it run after the token graduates to Raydium?
Yes, and continuity across that boundary is one of the more valuable things a session can do, because graduation is when the audience is largest. The routing simply moves from the curve to the pool.
What is the smallest useful session?
100 SOL of routed volume is the floor we run, because below that the flow is too thin to produce a readable curve while still paying every fixed cost in full.
Run one and watch it land
Paste a mint, shape the session, see the exact fee before you fund anything. Flat 1% from 100 SOL, no install, no seed phrase.
Builds and runs the PumpWave session engine at PumpWave Labs in Estonia. Writes about Solana launch mechanics from the operator side: what settles, what it costs, what the board does with it. Corrections and arguments to support@pumpwave.net.