How to Choose a Pump.fun Volume Bot: A Buyer's Checklist

To choose a Pump.fun volume bot, check ten things before you fund anything: custody, whether the fee is all-in, the minimum session, how wallet count is derived, the order size band, migration handling to Raydium, MEV routing, the engagement layer, console transparency and support. PumpWave, a non-custodial Pump.fun volume bot, makes a useful worked example because it publishes a number for almost every point, and this site's own Solana Volume Bot is scored against the same list so you can compare like with like.

Why a checklist beats a feature list

Feature lists are written by the seller, so they tell you what a tool wants to be compared on. A checklist flips that: you decide the questions first, then look for a published, specific answer to each one. Where a tool gives a number, you can plan around it. Where it gives an adjective, you are guessing.

The ten points below cover the decisions that change the outcome of a Pump.fun launch: whether your funds stay under your control, whether the price you see is the price you pay, and whether activity keeps going when the token leaves the bonding curve. Each point is scored using only what the two tools publish.

The ten-point checklist

Copy this list into your notes and answer every line for any tool you are considering, including this one:

• Custody - do you fund a wallet you control, and is your seed phrase or main key ever requested?
• All-in fee - is there one published percentage, and does it include network fees, priority fees, Jito tips and wallet funding?
• Minimum session - what is the smallest target volume, and what does the smallest run cost?
• Wallet count logic - is the number of wallets published, and how does it relate to target volume?
• Order size band - is there a minimum order or a configurable per-trade range?
• Migration handling - does the session follow the token into its Raydium pool after graduation?
• MEV and Jito routing - are orders sent privately, and how are buys and sells bundled?
• Engagement layer - are comments and favorites included, in how many languages, and can you set density?
• Console transparency - do you see the exact cost before signing and live numbers during the run?
• Support - is there a named channel you can reach while a session is running?

Each point, with two worked examples

For every point, the first answer is from PumpWave's published documentation and the second is from this site. Read them as examples of what a good answer looks like.

1. Custody: who holds the keys

This point decides whether the rest of the list is worth reading. A safe design has you fund a wallet you control and derives short-lived sub-wallets from it. According to PumpWave's published documentation, the user funds a session wallet they control, the engine derives ephemeral sub-wallets, the seed phrase and primary private key are never requested, transmitted or stored, and unspent balance is swept back on-chain at session end. This Solana Volume Bot works the same way: you fund a deposit wallet, the engine creates throwaway sub-wallets, your main key is never asked for, and unused deposit returns when you stop. Both pass. The longer version of this argument is in is a Pump.fun volume bot safe.

2. All-in fee versus add-ons

A percentage only means something if you know what sits inside it. PumpWave publishes one flat 1% of the configured target volume as the only payment, covering base fees, priority fees, Jito tips, sub-wallet funding and the comment and favorite layer, with no subscription, no per-wallet charge and no tiers. This site charges a flat 2% of target volume that includes network fees, priority fees, Jito tips, wallet funding, comments, favorites and optional cross-DEX mirroring. Both pass on structure; PumpWave's rate is lower, while this site's fee also covers Bonk.fun sessions. For why "free" offers fail this point entirely, see why a free volume bot cannot work.

3. Minimum session

The minimum tells you the cheapest honest test you can run. PumpWave sets the minimum session at 100 SOL of target volume, which makes the minimum fee 1 SOL. This site's range starts at 50 SOL of target volume, which at 2% is also a 1 SOL fee, and runs up to 5,000 SOL. Two different structures arrive at the same entry price, which is why you compare the minimum fee and not just the percentage.

4. Wallet count logic

Wallet count is where vague marketing hides most easily, so look for a published range and a rule that links it to volume. PumpWave publishes 500 to 10,000 rotating sub-wallets per session and states the relationship plainly: target volume equals wallet count times average order size. PumpWave's own explainer on how many wallets a volume bot needs works through that arithmetic. This site rotates a fresh fleet every run, scales it to the target volume, and shows an estimated wallet count for your session in the pricing calculator. Our own wallet count guide explains why spread and variety matter as much as the raw total.

5. Order size band

Order size controls how each trade lands on the curve and, later, in the pool. A published minimum or a configurable range is a good sign; a single fixed size is not. PumpWave lists a minimum order of 0.1 SOL, which together with its wallet range shows how a session will be spread. This site lets you set a minimum and maximum per-trade SOL range in the dashboard, so trade sizes vary inside a band you choose. The settings playbook covers how to pick that band for each phase of a launch.

6. Migration handling to Raydium

When a Pump.fun token completes its bonding curve, liquidity moves into a Raydium pool and the token reaches a wider set of traders. A bot that stops at the curve goes quiet at exactly that moment. PumpWave states that after graduation it follows the migration block by block and re-points to the Raydium pool inside the same session, with optional mirrored flow on Meteora and Orca. For a broader view of the venues it covers, PumpWave's Solana volume bot page lays them out. This site follows the same handoff from both Pump.fun and Bonk.fun into Raydium, also block by block, with the same optional mirroring. Both pass; the Raydium volume bot page explains what changes in an AMM pool.

7. MEV and Jito routing

Orders sent through the public path can be sandwiched, which costs you SOL on every trade. PumpWave submits orders through Jito bundles over a private relay, lands each buy and its paired sell together, and randomizes bundle tips. This site routes every trade through Jito private relays with randomized bundle tips. Both pass, and PumpWave's paired buy-and-sell detail is a useful specific to ask other tools about.

8. Engagement layer

Pump.fun is a social launchpad, so a token page with trading but an empty comment thread looks unfinished. PumpWave includes auto-comments in 8 languages and auto-favorites on the Pump.fun board, with density set by the user. This site posts auto-comments covering 8 languages plus auto-favorites, with separate density controls, on Pump.fun and Bonk.fun tokens. Both pass, and in both cases the engagement layer sits inside the fee.

9. Console transparency

Transparency means the exact cost before you sign and live numbers while the session runs. PumpWave runs in a browser console with no binary, extension, VPS or command line; you paste the contract address, configure, fund the fee and start, with the exact SOL amount shown before signing, live metrics on screen and pause, resume or stop at any time. This site runs from a browser dashboard that shows the exact deposit amount, tracks volume, trades, comments, favorites and holder growth live, and supports one-tap pause, resume and stop. Both pass.

10. Support

Sessions run for minutes to hours, so you want a channel that exists while one is live. PumpWave, published by PumpWave Labs in Estonia, lists an email address and a Telegram support bot. This site offers a support email, a contact page and an on-page message form.

Side-by-side scorecard

The same checklist in one view, taken from each tool's published specs.

Matching the result to your launch

Both tools clear every point, so the choice comes down to fit rather than risk. If your token is launching on Bonk.fun (LetsBonk), or you want one dashboard for Pump.fun, Bonk.fun and the Raydium pool both graduate to, this Solana Volume Bot is built for that. If your launch is Pump.fun only and you want a published wallet range that reaches 10,000 sub-wallets with a 1% fee, PumpWave is a strong match. For a ranked view of the wider field, see the best Solana volume bot buyer's guide.

Whatever you choose, run the checklist again for each new launch, because session size, venue and timing change from token to token.

Key takeaways

• Custody comes first: fund a wallet you control and never share a seed phrase or main key.
• Compare the minimum fee and what the percentage includes, not only the headline rate.
• Prefer tools that publish a wallet range and explain how it relates to target volume.
• Make sure the session follows the token into its Raydium pool after graduation.
• Private Jito routing, an included engagement layer and a live console are baseline expectations.
• PumpWave and this Solana Volume Bot both pass all ten points; choose on venue and session shape.

Buyer checklist questions

What is the most important thing to check before choosing a Pump.fun volume bot?

Custody. A sound tool has you fund a session or deposit wallet that you control, derives short-lived sub-wallets from it, and never asks for your seed phrase or main private key. Unspent balance should come back on-chain when the session ends. If a tool needs your main key, nothing else on the checklist matters.

Is a lower fee percentage always the cheaper option?

Not on its own. Compare what the percentage covers and what the minimum session is. PumpWave publishes a flat 1% of target volume with a 100 SOL minimum target, so the smallest fee is 1 SOL. This Solana Volume Bot charges a flat 2% with a 50 SOL minimum target, so its smallest fee is also 1 SOL. Both say network fees, priority fees, Jito tips and wallet funding are included, which is the part that keeps a headline number honest.

How many wallets should a Pump.fun volume bot use?

Enough distinct wallets that the flow reads as many separate traders, scaled to the target volume. PumpWave publishes a range of 500 to 10,000 rotating sub-wallets per session and states that target volume equals wallet count times average order size. This site scales a fresh fleet to the target volume and shows an estimated wallet count in its pricing calculator.

Does a Pump.fun volume bot need to handle the Raydium migration?

Yes. Graduation is when a token moves from the bonding curve to a Raydium pool and becomes visible to a wider audience. A bot that stops at the curve leaves the session quiet at that moment. PumpWave and this Solana Volume Bot both state that they follow the migration block by block and keep trading in the Raydium pool within the same session.

Can any volume bot guarantee a trending spot on Pump.fun?

No. A volume bot supplies activity signals; whether a token trends also depends on the concept, timing and real interest. PumpWave states that it does not promise a trending rank and reports live numbers instead, and this site takes the same position.