A Pump.fun bump bot places small, frequent trades on a token so it keeps registering fresh activity and stays near the top of views sorted by recent trading. It optimises for trade count and spacing rather than SOL volume. On PumpWave the same job is a session shape: many wallets, an order band near the 0.1 SOL floor and a length that keeps the gap between trades short, for a flat 1% of target volume.
Short version
- Bumping is about frequency: how many fresh trades land and how evenly they are spaced, not how much SOL is behind them.
- Pump.fun has not published its ordering rules, but it records the time of the last trade for every token, and a steady stream of trades keeps that time current.
- One wallet bumping over and over shows up as one trader in the trade list. Distinct wallets show up as a crowd.
- Gaps matter more than bursts. Fifty trades in one minute followed by silence leaves a token looking stale again within minutes.
- On PumpWave a bump job is configured, not bought separately: more wallets, a lower band, a shorter window.
What does bumping mean on Pump.fun?
The word comes from forum culture, where a new reply bumps a thread back up the list. On Pump.fun the same idea is applied to tokens: a trade lands, the token registers fresh activity, and any view ordered by recent activity moves it back toward the top. A bump bot exists to make that happen on a schedule, with small trades placed often enough that the token never looks idle.
Pump.fun has not published its ordering rules, and it has redesigned its board more than once, so treat any precise claim about weights with suspicion. What can be observed is what the site records. The coin data the Pump.fun front end loads includes, for every token, the timestamp of its last trade, the timestamp of its last reply and its reply count, alongside market cap and curve progress. A platform tends to sort on what it records, and a token whose last trade was seconds ago reads very differently from one whose last trade was an hour ago, both on the board and on its own page.
How is a bump bot different from a volume bot?
The two overlap heavily, and most tools that do one can do the other. The difference is what each one optimises for.
| Bump bot | Volume bot | |
|---|---|---|
| Optimises for | Number of trades and the gap between them | SOL routed over the session |
| Order size | As small as the tool allows | Sized to reach a target volume |
| Main thing it moves | Recency of activity and trade count | Traded volume, with trade count alongside |
| Typical shape | Short, regular intervals | A target spread over a window |
| Weak point | Little notional, so volume-ranked views barely notice | Large, sparse orders leave long quiet gaps |
Some bump tools place very small buys to keep the cost per bump low. On PumpWave the minimum order is 0.1 SOL, so every bump also carries notional. The practical effect is that a bump-shaped session moves the recency signal and the volume counter at the same time, which matters once a token reaches boards that weigh volume as well as activity.
Why do spacing and distinct wallets matter for bumping?
Spacing first. A recency-ordered view only holds a token near the top while trades keep arriving. A burst of fifty trades in one minute puts it there for that minute; after that the token is ordered by its last trade like everything else, and the burst is spent. The same fifty trades spread over ten minutes keep it current for ten minutes. Even spacing with some natural variance between orders is what a bump job actually needs.
Then wallets. Anyone who opens the token page sees the trade list, and a single address appearing in every row reads as one trader talking to themselves. Distinct makers are also counted by boards the token meets later: DexScreener's trending documentation lists transactions and unique makers among the inputs it weighs. This is why bump sessions work best wide, with many wallets each placing a few orders, and it is the same trade-off covered in how many wallets a volume bot needs.
How many trades per minute does a bump session produce?
The arithmetic is simple. Target volume is wallets multiplied by the average order, so the number of buys is roughly the target divided by the average order, and dividing by the session length gives the rate. The table counts buys only; the sells in a session add further trades beyond the rate shown.
| Session | Target | Buys | Rate | Fee |
|---|---|---|---|---|
| 500 wallets, 0.10-0.30 SOL, 60 min | 100 SOL | About 500 | One every 7 seconds | 1 SOL |
| 1,000 wallets, 0.10-0.14 SOL, 60 min | 120 SOL | About 1,000 | One every 3.6 seconds | 1.2 SOL |
| 1,000 wallets, 0.10-0.14 SOL, 15 min | 120 SOL | About 1,000 | More than one a second | 1.2 SOL |
| 2,500 wallets, 0.10-0.14 SOL, 3 hours | 300 SOL | About 2,500 | One every 4.3 seconds | 3 SOL |
Two levers do most of the work. Pulling the band down toward the 0.1 SOL floor buys more trades per SOL of target. Shortening the window raises the rate but ends the bumping sooner. A launch push wants the third row; a token that needs to keep looking alive through a slow afternoon wants the fourth.
Every one of those trades is a Solana transaction, and each signature pays the base fee set out in the Solana fee documentation, plus priority fees and tips when the network is busy. That is why bump jobs priced per transaction get expensive quickly. On PumpWave those network costs, the swap fee on every trade, token account rent and the funding of the session wallets are all inside the flat 1%.
How do you set up a bump-style session on PumpWave?
Paste the mint
Any public Pump.fun mint, whether you created the token or not. The console runs in the browser, with nothing to install.
Push wallets up, pull the band down
Choose between 500 and 10,000 rotating session wallets and set the band close to the 0.1 SOL floor. Keep the target at 100 SOL or more.
Choose the length that sets the spacing
From a 15 minute burst to a 10 hour run. Shorter windows bump harder and stop sooner; longer windows keep the token current for longer at a lower rate.
Add replies and favorites
A token that trades every few seconds with an empty reply thread looks unfinished. The comment layer posts lines in 8 languages, and auto-favorites come from distinct wallets.
Send the fee and watch it run
You send only the fee, 1% of target volume, with no seed phrase, private key or wallet connection. Orders go out as Jito bundles over a private relay, and routing follows the token into its AMM pool if it migrates mid-session.
Bundling matters more for frequent small orders than for occasional large ones. Jito's documentation describes a bundle as a list of up to five transactions that execute sequentially and atomically, all or nothing, which keeps a high-rate session landing in order. How the comment layer is tuned is covered in the Pump.fun comment bot guide, and what happens to bumping after graduation is in the PumpSwap volume bot guide.
What can a bump session not do?
It cannot promise a position. Where a token sits in any view at any moment also depends on everything else launched in the same window, and on a busy afternoon the competition for the top rows is fierce. It cannot create holders who stay, and it does not set a price: wallets that buy and sell inside the session add activity, not lasting demand. The full version of that argument is in does a volume bot get you trending.
What it does reliably is keep a token registering trades, from distinct wallets, at the rate you configure, for as long as you configure. The product overview of the console is on the Pump.fun volume bot page. Rules on automated trading and marketing differ by country, this is not legal advice, and activity should never be presented to buyers as something it is not.
Questions people actually ask
What is a Pump.fun bump bot?
A Pump.fun bump bot is a tool that places small, frequent trades on a Pump.fun token so it keeps registering fresh activity. The aim is to stay near the top of views ordered by recent trading and to make the token page look active to anyone who opens it.
Does bumping still work on Pump.fun?
Pump.fun has changed its board several times and does not publish how its views are ordered. It does record the last trade time for every token, and steady trading keeps a token looking active on its page and in recency views. How much that lifts it at any given moment depends on the competition, so no tool can promise a position.
Is a bump bot the same as a volume bot?
Not quite. A bump bot optimises for the number and spacing of trades, while a volume bot optimises for SOL routed. A session with many wallets, a low order band and a short window covers both at once.
How small can a bump order be on PumpWave?
The minimum order is 0.1 SOL. Every order is drawn at random inside the band you set, and the session target has to reach 100 SOL, so the fee starts at 1 SOL.
How many wallets does a bump session need?
More than most people expect. Each wallet adds a distinct maker to the trade list, and a wide fleet placing a few orders each reads very differently from a few wallets trading constantly. Sessions run from 500 to 10,000 wallets.
Does bumping continue after the token migrates?
Yes. Routing follows the token through the bonding-curve migration into its AMM pool, which is PumpSwap for current Pump.fun launches and Raydium for older ones, so the trade rate carries on inside the same session.
Run one and watch it land
Paste a mint, shape the session, see the exact fee before you pay anything. Flat 1% from 100 SOL covers every network and swap cost, no install, no seed phrase.
The people who build the PumpWave session console. We write about Solana launch mechanics from the operator side: what settles on chain, what a session costs and what the board does with it. Corrections and arguments to support@pumpwave.net.