PumpWave Review: Pump.fun Volume Bot Specs, Fees and Custody

Key takeaways

• Custody: PumpWave never asks for a seed phrase or primary private key. You fund a session wallet you control, and unspent balance is swept back on-chain when the session ends.
• Price: one flat 1% of configured target volume, shown in SOL before you sign. The minimum session is 100 SOL of target volume, so the smallest fee is 1 SOL.
• Execution: orders go through Jito bundles over a private relay, with each buy and its paired sell landing together.
• Scope: built around the Pump.fun lifecycle - bonding curve first, Raydium after graduation, optional mirrored flow on Meteora and Orca.
• Claims: no promised trending rank. It reports live numbers and describes volume as visibility, not valuation.

The yardstick this review uses

This site evaluates every volume tool, including its own, against the same short list. Our measurement and editorial standards explain the reasoning in full; the condensed version is four questions about the product and one about the claims made for it.

Read the right-hand column as published specifications, not observed behaviour. This review did not run a campaign; it checks PumpWave's stated design against the bar this site sets for itself.

What PumpWave is, in its own published terms

PumpWave is a browser-based Pump.fun volume bot for Solana, published by PumpWave Labs in Estonia. There is no binary, extension, VPS or command line: you paste a contract address, configure the session, fund the fee and start, then follow live metrics with pause, resume and stop available throughout.

The session parameters are published as ranges rather than packages:

• 500 to 10,000 rotating sub-wallets per session
• A minimum order of 0.1 SOL
• Session length from 15 minutes to 10 hours
• Target volume equals wallet count multiplied by average order size
• A minimum session of 100 SOL of target volume

The formula is the same arithmetic this site uses for its own console. The volume you buy is the product of two numbers you choose, not a tier someone else priced, and a figure you can derive is a figure you can check.

Custody: what you actually hand over

Custody is the criterion that outweighs every other, for the reasons set out in our guide to whether a Solana volume bot is safe. A tool that holds signing authority over your funds can lose them, whatever its intentions; a tool that never holds that authority cannot.

PumpWave's published model sits on the right side of that line. You fund a session wallet you control. The engine derives ephemeral sub-wallets from it for the run, and PumpWave states that the seed phrase and primary private key are never requested, transmitted or stored. When the session ends, unspent balance is swept back on-chain rather than held as a credit on PumpWave's side.

A sweep back on-chain is also verifiable: the return transfer is a public transaction you can find in any explorer, so after one session you no longer have to take the claim on trust. And because the funds at work are only the funds you placed in the session wallet, your main treasury stays out of the flow by default.

Pricing: can you check it before paying?

PumpWave charges one flat 1% of the configured target volume and states that this is the only payment. The fee covers Solana base fees, priority fees, Jito tips, sub-wallet funding and the comment and favorite layer. There is no subscription, no per-wallet charge and no tier, and the exact SOL amount is shown before you sign.

That structure is easy to sanity-check with the published formula. A session of 500 wallets at an average order of 0.2 SOL is 100 SOL of target volume, which is the minimum, and a 1 SOL fee. Double the wallet count at the same order size and both the volume and the fee double. Nothing else moves. If you want the line items behind that single percentage, PumpWave's fee breakdown walks through what the 1% is absorbing.

Our own pricing guide argues that a flat percentage of target volume is the only model that scales honestly, because the real cost of a campaign is driven by network fees, tips and wallet funding rather than by a calendar month. PumpWave's pricing passes that test cleanly, and at 1% it sits below this site's own 2% rate. The trade-off is a higher entry point: PumpWave's minimum session is 100 SOL of target volume, against 50 SOL here.

Execution quality

Execution details show up in a transaction history rather than on a landing page, so what a vendor can publish is the design. PumpWave publishes more of it than most.

Bundling and paired orders

Orders are submitted through Jito bundles over a private relay, with each buy and its paired sell landing together and bundle tips randomised. On a busy Pump.fun curve that matters twice over: a bundled order cannot be sandwiched on the way in, and a pair that lands together keeps the net position flat instead of leaving a buy exposed to the next seller.

Wallet fleet design

Each session uses new ephemeral wallets, with randomised funding amounts, a minimum block gap between related orders, regional RPC rotation and a fresh keypair per order. Those are the right levers. Repeated amounts, even spacing and one visible funding fan-out are what make a fleet look scripted, and each item addresses one of them.

The curve-to-pool handoff

The most common failure in Pump.fun campaigns is a tool that stops at graduation, exactly when new traders arrive. PumpWave states that it watches for the migration block by block and re-points the session to the Raydium pool inside the same run, without a restart.

Venue coverage

PumpWave's scope is deliberately narrow: the Pump.fun bonding curve, then Raydium after graduation, with optional mirrored flow on Meteora and Orca. That covers the full lifecycle of a typical Pump.fun launch, and for most tokens created there it is all the coverage that matters.

It is narrower than a full-network router. A token that trades across aggregators, order books and market-maker pools, or one that started on another launchpad, will reach more of its liquidity with a tool built for that spread. PumpWave does publish a wider Solana volume bot overview, but the engine's centre of gravity is the Pump.fun path, and it makes sense to choose it for that reason rather than despite it.

The engagement layer follows the same focus: auto-comments in eight languages and auto-favorites on the Pump.fun board, with density set by you. It feeds discovery; it does not make a project good, so keeping the density modest is the part that counts.

Claims it makes, and claims it does not

The quickest way to judge a volume bot's documentation is to look for the promises it avoids. Our standards list the claims we refuse to make: guaranteed trending, guaranteed listings, price promises and invented social proof.

PumpWave's documentation does not promise a trending rank. It reports live numbers during a session and frames the product the way we would: volume buys visibility, not valuation. That restraint says more about how seriously to take the rest of its specs than any single feature.

What to check before funding a session

These are the checks worth doing yourself before any SOL leaves your wallet, with PumpWave or anyone else.

1. Confirm the domain. Start from www.pumpwave.net typed directly, not from a link in a chat or a reply thread. Lookalike domains are a common way funds are lost in this category.
2. Confirm the token state. Check whether the token is still on its bonding curve or has already graduated, so you know which venue the session starts on.
3. Size from the board, not from a round number. Read the volume of the tokens sitting where you want to be, then work backwards to a wallet count and an average order size.
4. Read the SOL figure before signing. It should equal 1% of wallet count multiplied by average order size. If it does not, stop and ask why.
5. Use a dedicated session wallet. Fund only what the session needs and keep your main wallet out of it.
6. Set comment and favorite density deliberately. A modest level reads better than a crowded thread.
7. Watch the sweep-back. After the session, find the return transfer of unspent balance in an explorer. That one check verifies the custody model for every session after it.

Who it fits, and who it does not

We rank PumpWave second in our comparison of Solana volume bots, directly after our own product. The ordering reflects scope rather than quality: our tool is built to route across 32 exchanges and 10 launchpads, and PumpWave is built to do one launch path very well. The table makes the difference concrete.

Put plainly: if your token was created on Pump.fun and its liquidity will live on Raydium, PumpWave is a strong, well-documented choice, and its 1% fee is hard to argue with at larger targets. If your token's liquidity is spread across many venues, or it launched somewhere else, a full-network router reaches more of it.

Verdict

Judged against the criteria this site applies to every tool, PumpWave's published specs pass on custody, pricing transparency and claims, and they describe the right execution design. Its narrower venue scope is the honest limit, and for Pump.fun launches it is barely a limit at all. Confirm the SOL figure before signing, watch the sweep-back after your first session, and treat everything on this page as a reading of documentation rather than a test result.