Rotating wallet fleet
Each session mints a new batch of ephemeral Solana wallets and seeds them with randomized amounts, so no two fund alike and nothing carries a signature from your previous launch into this one.
The Pump Fun Volume Bot built to get a launch noticed.
A precision Pump.fun volume bot for Solana launches. Up to 10,000 rotating wallets, multilingual auto-comments, auto-favorites and anti-MEV Jito routing fire as one engine, building the on-chain footprint that carries a token into trending and through the Raydium migration.
Watch a 300 SOL session configured end to end in the live console
What is a Pump.fun volume bot?
A Pump.fun volume bot is an automation layer that produces real on-chain trading volume for a Solana token by driving many independent wallets through timed buys and sells on Pump.fun and, after migration, on Raydium. The orders settle on mainnet like any other swap, so the routed volume, transaction count and unique-holder curve that Pump.fun ranks on all move together.
- Non-custodialKeys never leave your wallet
- Flat 1% feeNetwork fees and tips included
- 500 to 10,000 walletsRotating fleet, fresh every session
- Browser consoleNo install, no command line
The distinction that matters is where the orders come from. One wallet trading against itself moves a chart but leaves a single address on every fill, which is exactly the pattern buyers check for. A volume bot spreads the same flow across hundreds or thousands of independent wallets, spaces the fills in time and varies order sizes, so what a scout sees is a market with participants rather than a loop.
PumpWave adds the layer that pure trading misses: the Pump.fun board itself. Comments and favorites feed how a token is ranked and how a visitor decides in the first ten seconds, so the engine drives them from the same fleet, in the same window, at a density you set.
Three moves. No terminal required.
The whole session lives in a browser console: verify a mint, shape the run, watch the tape move.
- 01 / paste
Verify the token
Drop the Pump.fun contract address into the console. Public on-chain metadata is read back - bonding-curve progress, liquidity and current pool - so you can confirm you are aiming at the right mint before anything is funded.
pumpwave> token 7xKXt...pump - 02 / shape
Shape the session
Choose target volume, wallet count, order band, buy share, comment and favorite density, and the curve the session should follow. The fee and the projected footprint update as you move each control.
pumpwave> volume 250 --curve burst - 03 / run
Launch and watch
Fund the flat fee and start. Routed volume, confirmed transactions, unique holders and time remaining stream back to the same screen, and you can pause, resume or stop at any moment.
pumpwave> start --live
The console, in motion.
A working preview of the session interface: execution log, routing mesh and throughput counters, exactly as they behave while a campaign runs.
session telemetrysimulated preview
—
execution_logtail · 0 errors
routing_mesh16 nodes · sim
tx / s0
bundle tip0.0018
slot lag1
solana-mainnet
jito-relay · 12 ms
private-rpc · pool #04
illustrative interface - not live platform data
Every module a Solana volume bot should ship with.
Execution, social signal and traceability are tuned against live Pump.fun launches, then exposed as switches you control.
Bundle-speed execution
Orders go straight to the validator inside Jito bundles, so confirmations stay tight even when the network is busy.
Anti-MEV routing
Private relay submission keeps every order out of the public mempool, where sandwich bots would otherwise skim the volume you paid for.
Human-shaped timing
Intervals follow a Poisson distribution and order sizes vary inside your band, so the tape reads like independent traders rather than a loop.
Pump.fun to Raydium, without the gap.
The moment a token graduates off the bonding curve, execution re-points at the new Raydium pool inside the same session. Momentum does not pause at the exact minute new buyers show up.
Pump.funRaydium
Metrics while it runs
Routed volume, confirmed transactions, unique holders and buy pressure refresh on the same screen you launched from.
Non-custodial by design
The deposit wallet is yours. No seed phrase is requested, no primary key is transmitted, and sub-wallets are discarded when the session closes.
Stop and get the rest back
End a session at any point and the unspent balance returns to your wallet on-chain. No ticket, no waiting period, no lock-up.
Volume is the start. This is the whole engine.
Dozens of modules run in concert so the footprint your token leaves behind reads like a crowd that found it, not a script that ran.
signature
Auto-comments in eight languages
A curated library is shuffled, emoji-weighted and posted with an organic typing rhythm, so the board fills with lines a native speaker would actually write.
sampled from the library8 languagesnative phrasing
interactive
Buy / sell balance
Dial pressure from aggressive accumulation to balanced rotation. The engine honors the ratio down to the individual transaction.
Auto-favorites
Separate wallets star the token, which feeds the most-watched board where scouts look first.
Reply threads
The engine answers real questions on the board in context instead of dropping one-line noise.
Sentiment mixer
Set the share of bullish, neutral and skeptical lines so the board does not read like a wall of shills.
Typing cadence
Per-character delay noise removes the instant-paste signature that moderation tools flag.
Wallet personas
Whale, retail, builder and skeptic archetypes each carry their own size, rhythm and vocabulary.
Native phrasing
Regional slang written per language rather than machine translation, so it lands with native readers.
Holder pacing
New wallets join on a growth curve, so unique holders climb steadily instead of jumping in one block.
Waking-hours weighting
Comment and trade density follow the clock in your target regions instead of humming flat all day.
tunable
Order size band
Set a floor and a ceiling in SOL. Sizes are drawn from inside your band along a bias curve you choose, never from a fixed amount.
curve presets
Session shape
Pick how the session distributes its volume over time: a slow build, a launch spike, a quiet accumulation or a whale-led run.
Interval control
Gaps from seconds to minutes with Poisson jitter, so no two waits repeat.
Micro and macro mix
Small orders sprinkled between occasional large swings, the way a real tape actually prints.
Priority-fee auto-tune
Priority is recalculated against live network load to keep the confirm rate high.
Jito bundle routing
Private relay submission with randomized tips so bundles cannot be fingerprinted.
Adaptive slippage
Per-order slippage is derived from live pool depth, which means fewer failed swaps.
Burst windows
Short high-intensity spikes aligned to the minute edges that ranking jobs sample.
Fresh fleet per run
Every session spawns clean addresses, so nothing links this launch to the last one.
Randomized dispersal
Your deposit is split into uneven amounts before it ever reaches a sub-wallet.
Dust sweep
When the session ends, residual balances are collected and returned in one pass.
Regional RPC spread
Sub-wallets submit through geo-diverse endpoints instead of one datacenter.
Cluster spacing
Spacing rules stop your wallets from forming a recognizable shape on bubble maps.
Aged-wallet option
Longer sessions can draw on addresses with prior history when extra realism matters.
Sandwich shield
Private submission means searchers never see the order before it lands.
Pair delays
Randomized micro-gaps keep matched orders from looking scripted to scanners.
Route diversity
Validator hops rotate so confirmations do not arrive on a metronome.
Per-signature keys
Each signature uses an ephemeral keypair, so there is no address to fingerprint.
Block-gap rule
No two fleet orders land in adjacent blocks, which is what pattern detectors look for first.
Funding noise
Seed amounts carry random decimals, breaking the identical-transfer heuristic.
Threshold timing
Volume, holders, comments and favorites are timed to cross ranking thresholds together.
Raydium switch
Migration is detected block by block and execution re-points with no downtime.
Aggregator shape
Flow is shaped to register on Dexscreener and Dextools hot-pair logic.
Unique-holder bias
Weighting toward fresh addresses lifts the holder count buyers check first.
Scheduled launch
Arm a session to start just before your announcement so arrivals meet a moving chart.
Cross-DEX mirror
After migration, mirror flow across Meteora and Orca for wider listing coverage.
One console
Every switch lives on a single screen with live status and inline alerts.
Pause and resume
Freeze mid-session when organic buyers arrive, then pick the session back up.
Scheduled start
Arm the engine for a precise UTC timestamp instead of watching a clock.
Multi-token
Run several tokens in parallel from one account, each with its own configuration.
Saved presets
Store a configuration that worked and fire it again on the next launch.
Instant refund
Unused deposit returns the moment you stop, with no support ticket in between.
Live analytics
Volume, holders, buy pressure and rank stream continuously while the session runs.
CSV export
Export every transaction and wallet for your own post-launch review.
Volume bot, bundler or paid callers?
Three approaches get used at launch and they solve different problems. Here is what each one actually produces on-chain.
| Approach | What happens | Signal produced | Main weakness |
|---|---|---|---|
| Volume bot session | Many independent wallets trade the token over a defined window | Volume, transactions, holders and board activity rise together | If funding, timing or sizing repeats a pattern, clustering tools can flag the fleet |
| Bundler at launch | One block buys a large share of supply at mint | Supply concentration, almost no sustained volume | Visible on holder-distribution maps and often punished by buyers |
| Paid callers only | External audiences are pointed at a static chart | Attention with no on-chain confirmation | Traffic arrives, meets a flat tape and leaves |
| No volume tactic | The token relies entirely on unprompted buyers finding it | Volume and holders reflect real demand only, with no floor | New tokens with no early activity are skipped by scouts before buyers see them |
Is a Pump.fun volume bot safe?
The honest version, including the parts a sales page usually leaves out.
A volume bot moves real SOL through real wallets on Solana mainnet. There is no simulation layer, so the ordinary risks of on-chain activity apply: congestion can slow confirmations, and a session that does not reach the window you were aiming at still spends the fee it was configured with.
PumpWave is non-custodial, which removes the largest failure mode - nobody here can move funds you did not commit to a specific session, and your seed phrase is never requested. What stays on you is the SOL you fund and the contract address you paste, because an order routed to the wrong mint cannot be recalled.
Wallet clustering detection is a real and improving field. Randomized funding, enforced block gaps and regional RPC rotation raise the cost of linking a fleet together; they do not make it impossible. Size a session the way you would size any other marketing spend, and read the terms before funding one.
Session limits, on the record.
The numbers the console enforces, so you can size a run before you open it.
| Parameter | Value |
|---|---|
| Wallets per session | 500 to 10,000 rotating sub-wallets |
| Minimum session volume | 100 SOL of target volume |
| Minimum order size | 0.1 SOL per trade |
| Session length | 15 minutes to 10 hours |
| Venues | Pump.fun bonding curve, Raydium, Meteora, Orca |
| Transaction routing | Jito bundles over a private relay |
| Engagement layer | Auto-comments in 8 languages, auto-favorites |
| Fee model | Flat 1% of target volume, the only payment |
| Custody | Non-custodial - keys never leave your wallet |
| Setup | Browser console, no install and no code |
One number. Nothing behind it.
You set the target volume, from 100 SOL upward. PumpWave takes a flat 1% fee on it and that is the entire invoice - base fees, priority fees, Jito tips, wallet funding, comments and favorites all sit inside that one number.
target volume
250SOL
fee · flat 1%
2.5SOL
shape the sessionevery parameter is yours
40%
70%
72%
session previewlive estimate
wallets deployed2,120
orders executed2,500
comments posted1,000
favorites starred1,484
est. unique holders1,314
est. session length45m
These figures are illustrative and scale with your inputs. Real output depends on live network conditions and on how crowded the trending window is at that moment.
What this engine will not promise you.
PumpWave reports what settles on-chain: routed volume, confirmed transactions, unique holders, comments and favorites. Everything below is outside a volume bot.
- It does not promise a trending rank. That feed also weighs the tokens competing in the same window and the organic interest a token already has.
- It does not promise a price outcome or a profit. Volume changes on-chain activity, not external demand.
- It does not make a wallet fleet invisible. It reduces the patterns clustering tools look for, which is a different claim.
- It does not give legal advice. Rules on engineered volume differ by jurisdiction and stay with the operator of the session.
Terms used on this page.
Plain definitions for the vocabulary a Pump.fun volume bot runs on.
- Bonding curve
- The algorithmic pricing curve Pump.fun uses from the moment a token is minted until it raises enough SOL to migrate to Raydium.
- Jito bundle
- A group of Solana transactions submitted together through a private relay, so they either all land in the same block or none of them do.
- MEV
- Maximum extractable value: the profit a searcher bot makes by reordering, inserting or front-running transactions it sees in the public mempool.
- Wallet clustering
- The on-chain technique analysts use to link separate addresses back to one operator by matching funding amounts, timing and submission routes.
- Wash trading
- One party trading with itself to fake volume. A rotating fleet of independent wallets with variable sizing is a different on-chain shape, but the resulting volume is still engineered rather than organic demand.
- Raydium migration
- The handoff that happens when a Pump.fun bonding curve completes and the token starts trading in a Raydium AMM pool instead.
Who runs PumpWave.
PumpWave is published by PumpWave Labs, registered in Estonia. The engine is built and maintained by Kristjan Kask, Founder, who also writes and keeps this page current: when the fee, the wallet range or the venue list changes, the copy here changes the same day.
Support runs through support@pumpwave.net and the public Telegram channel linked in the footer. There is no phone line and no ticket portal, because every question so far has been answerable in writing.
Questions, answered plainly.
What the engine does, what it costs, what it will not promise you.
01What is a Pump.fun volume bot?
A Pump.fun volume bot is software that creates genuine on-chain trading activity for a Pump.fun token by coordinating a fleet of separate Solana wallets that buy and sell on a schedule you define. Because every order settles on mainnet, routed volume, transaction count, holder growth and board engagement rise together instead of a single wallet churning the same position.
02How does PumpWave push a token into the Pump.fun trending feed?
PumpWave drives the four signals the Pump.fun trending feed reads: trade frequency, routed volume, unique holders and board engagement. A rotating wallet fleet places time-spaced buys and sells, a separate engagement layer posts native-language comments and favorites from distinct wallets, and the buy/sell balance is shaped so volume climbs across the session instead of spiking once. Where a token ranks against the launches competing in the same window is not something any tool can guarantee.
03Is PumpWave non-custodial?
Yes, PumpWave is non-custodial. You fund a session wallet that you control, and the engine derives ephemeral sub-wallets from that deposit. Your seed phrase and primary private key are never requested, never transmitted and never stored. When a session ends the sub-wallets are swept and anything you did not spend returns to your wallet on-chain.
04What does a session cost?
One flat 1% fee on the target volume you configure, with a minimum session size of 100 SOL of target volume. A 100 SOL session therefore costs 1 SOL. That single number covers Solana base fees, priority fees, Jito bundle tips, sub-wallet funding and the entire engagement layer. There is no subscription, no per-wallet charge and no upsell tier.
05Is there anything to pay beyond the fee?
No, the flat 1% fee on target volume is the only payment. Network fees, priority fees, Jito tips, wallet funding, comments and favorites are all inside it, and the console prints the exact SOL amount before anything is signed. If a tool quotes a low headline rate and then asks for separate gas top-ups, you are paying twice for the same session.
06How many wallets can one session run?
Sessions scale from 500 to 10,000 rotating wallets, start at 100 SOL of target volume and use a floor of 0.1 SOL per order. Target volume is simply wallet count multiplied by average order size, and the console recalculates it live while you move the sliders. Duration is yours too, from a 15-minute burst to a 10-hour grind.
07What happens when the token migrates to Raydium?
Nothing stops when a token migrates to Raydium. The engine watches the bonding curve block by block, detects the graduation, and re-points execution at the new Raydium pool inside the same session. Optional mirroring extends the same flow to Meteora and Orca so aggregator listings keep updating while new buyers arrive.
08What is anti-MEV Jito routing?
Searcher bots watch the public mempool and profit by front-running predictable orders, a practice known as MEV or maximum extractable value. PumpWave submits through Jito bundles on a private relay, so a buy and its paired sell land together and cannot be sandwiched. Tips are randomized per bundle, which also stops your traffic from carrying a repeatable fingerprint.
09Can wallet clustering tools trace the fleet?
PumpWave reduces, and does not eliminate, the signals cluster analysis relies on. It randomizes the funding amount of every sub-wallet, enforces a minimum block gap between related orders, rotates RPC endpoints across regions and signs each order with a fresh keypair. Clustering tools normally link wallets by identical funding amounts, adjacent-block timing and shared submission routes, and those are the three patterns this session design avoids.
10Do I need to install anything or run a script?
No install and no script are needed. Everything runs in the browser console: paste a contract address, shape the session, fund it, press start. There is no binary to download, no extension, no VPS and no command line. Live metrics stream back to the same screen while the session runs.
11How quickly does a session show results?
Routed volume and transaction counts appear within the first minutes because orders settle at Solana block speed. Where a token lands on the trending feed depends on the tokens competing in that window, your target volume and existing organic interest, so PumpWave reports live numbers instead of promising a rank.
12Is there a free Pump.fun volume bot?
There is no free Pump.fun volume bot in any meaningful sense. Every order a volume bot places pays a Solana base fee, a priority fee and, on a private relay, a bundle tip, and the sub-wallets themselves have to be funded. A tool advertised as free either hides those costs inside a minimum deposit, monetises your private key, or runs so few orders that the tape never moves. PumpWave charges one visible 1% fee and pays those costs out of it.
13What makes one Pump.fun volume bot better than another?
Four things separate one Pump.fun volume bot from another, and all four are verifiable before you fund anything: whether it is non-custodial and never asks for a seed phrase, whether the fee is a single number that already covers network costs, what the minimum session size is, and whether execution survives the Raydium migration. Fleet size matters less than fleet behaviour - 10,000 wallets funded with identical amounts in adjacent blocks read as one actor, while a few hundred well-spaced wallets do not.
14Is a Pump.fun volume bot legal?
Whether a Pump.fun volume bot is legal depends on where you are and what you claim to other people, and PumpWave does not give legal advice. Engineered trading volume, wash trading and market manipulation are treated differently across jurisdictions, and presenting bot-driven volume to investors as organic demand can carry consequences whatever tool produced it. PumpWave Labs is registered in Estonia; confirming what is permitted where you operate stays with you.
15Can a volume bot make a token price go up?
A volume bot does not push a token price up directly. It changes on-chain volume, transaction count and holder count - it does not create external demand. Price still depends on real buyers deciding to enter and hold after they arrive, and a session that ends with no organic buying usually sees price drift back toward where it started. Volume buys visibility, not a valuation.
16What happens if I stop a session early?
The session halts at the next completed order. Sub-wallets holding an unspent balance are swept and anything not already spent on trades, fees or tips returns on-chain to your deposit wallet. Volume and transactions already routed stay on-chain, because settled orders cannot be reversed.
17Can I run a session on any Pump.fun token?
The console accepts any public Pump.fun contract address, so you do not have to be the token creator. It reads public on-chain metadata only - bonding-curve progress, liquidity and the current pool - which is why checking the address you paste is your own responsibility before funding.
Want the long version? Read the Pump.fun volume bot operator guide - on-chain mechanics, the full cost stack in SOL and the settings that change how a session reads.
Your next Pump.fun launch is three fields away.
Open the console, paste a contract, set a target volume and watch the routed volume update live.
Launch the volume bot