A PumpSwap volume bot routes buys and sells through the PumpSwap pool a Pump.fun token trades in after its bonding curve completes, so the chart stays active once the token has migrated. On PumpWave you paste the mint, the session trades on the curve while the curve is open, follows the token across the migration and keeps routing in its PumpSwap pool, all for a flat 1% of the target volume from 100 SOL.
Short version
- PumpSwap is the constant-product AMM run by Pump.fun. Current launches move there when the curve completes; older launches went to Raydium.
- After migration, price comes from the ratio between two reserves, so order size has to be read against pool depth rather than as a fixed SOL figure.
- A pool with one trade is enough for DexScreener to list the pair automatically, which opens a second audience.
- Migration is when attention peaks. A session that stops at the boundary goes quiet at the worst possible moment.
- On PumpWave routing follows the token into its pool on its own, and the flat 1% covers every swap on either side of the boundary.
What is PumpSwap?
PumpSwap is the decentralized exchange Pump.fun launched in March 2025 to receive tokens that finish their bonding curve. The PumpSwap program documentation that Pump.fun publishes describes it in one line: a constant-product AMM. Each pair lives in its own pool, and pools created by a migration use a canonical index, so every graduated token has one standard pool that tools can find.
Before PumpSwap existed, a completed curve was withdrawn and moved to Raydium by an off-chain process. That path still matters: tokens that graduated before the switch still trade in Raydium pools. For those, the logic in the Raydium volume bot guide applies. For anything launched on Pump.fun since, the pool is on PumpSwap.
How does a Pump.fun token get to PumpSwap?
A Pump.fun token starts life on a bonding curve that sells a fixed allocation of supply. When the last of that allocation is bought, the curve is marked complete and no more buys or sells are possible on it. According to the Pump program documentation, the liquidity from the completed curve is then migrated to PumpSwap, the LP tokens received from the new pool are burnt, and the migrate instruction is permissionless, so anyone can trigger it for a completed curve.
Three practical consequences follow. The mint does not change, so holders keep the same token and the same address. The starting liquidity stays in the pool, because the LP tokens that could withdraw it no longer exist. And there is a short gap between the final curve buy and the first pool trade, which is exactly where a session that only knows about the curve runs out of road.
What changes for volume after migration?
The job is the same: distinct wallets placing timed buys and sells. The environment those orders land in is not.
| Bonding curve | PumpSwap pool | |
|---|---|---|
| Price set by | How much supply the curve has sold | Ratio between the two pool reserves (x * y = k) |
| Slippage driven by | Position on the curve | Order size relative to pool depth |
| Order sizing rule | Absolute SOL amounts are fine | Read each order as a share of the SOL reserve |
| Where it is visible | Pump.fun board and token page | Pump.fun page plus DexScreener and other pool-level tools |
| Venue fee | Applies to every swap | Applies to every swap |
| Inside the flat fee | Yes, on PumpWave | Yes, on PumpWave |
The row that matters most for configuration is the second one. In a constant-product pool the reserves multiply to a fixed number, so a buy that adds SOL to one side removes tokens from the other and moves the price. How far it moves depends only on how large the order is relative to the reserves.
A worked example of depth
Take a 0.2 SOL buy. Into a pool holding 80 SOL on the quote side, it lifts the spot price by about half a percent. Into a pool holding 20 SOL, the same order lifts it by about 2 percent. Across a session of hundreds of orders, the second pool produces a chart that jumps on every print, while the first produces texture. That is why the order band should be chosen against depth once a token is in its pool, and why widening the band downward is a better way to add variety than raising its ceiling.
Does a PumpSwap pool get a token onto DexScreener?
DexScreener's token listing documentation states that tokens are listed automatically as soon as they are added to a liquidity pool and have at least one transaction. A freshly migrated token meets both conditions with its first pool trade, so the pair appears on its own. That makes the hour after migration the moment a token is in front of two audiences at once: the Pump.fun crowd that watched it graduate and pool-level scanners seeing it for the first time.
Being listed is not the same as trending. DexScreener's trending documentation names the inputs it weighs: volume, liquidity, transactions, unique makers and holders, plus visitors and reactions on its own pages. A session moves the first, third and fourth of those directly. It does not move liquidity depth, holder growth or page visits, which is why the honest answer to does a volume bot get you trending is sometimes, and never on its own.
How does a PumpWave session handle the migration?
Paste the mint
Any public Pump.fun mint works, whether the token is still on its curve or already trading in its pool. The console resolves it on chain before anything is configured.
Set wallets and the order band
Choose 500 to 10,000 rotating session wallets and an order band with a 0.1 SOL floor. Target volume is wallets multiplied by the average order, and the console recalculates it as you move the controls.
Pick a length that spans the boundary
Sessions run from 15 minutes to 10 hours. For a token close to completing its curve, a window that starts before migration and runs well after it keeps the tape continuous through the busiest moment.
Let routing follow the token
Orders go out as Jito bundles over a private relay. When the curve completes, routing follows the token into its AMM pool, which is PumpSwap for current Pump.fun launches and Raydium for older ones, inside the same session.
Send only the fee
The fee is a flat 1% of the target volume, from a 100 SOL target, which is 1 SOL. No seed phrase, no private key and no wallet connection are involved.
The fee covers the whole session on both sides of the boundary: Solana base and priority fees, Jito tips, the swap fee on every curve and pool trade, token account rent, funding of the session wallets, comments and favorites. You do not fund wallets or send trading capital. The line-by-line view of what a session would otherwise pay for is in how much a volume bot costs.
Should a PumpSwap session start before or after migration?
It depends on where the token is. For a token close to completing its curve, starting on the curve is the stronger choice, because the session is already running when graduation arrives and the first pool trades land on a chart that has momentum rather than one that just went quiet. For a token that migrated days or weeks ago, the session lives entirely in the pool, and a longer window with steadier flow suits pool-level boards better than a short burst.
In both cases, wallet count matters more than headline volume. A few hundred wallets each placing one or two orders read as a crowd; a handful of wallets cycling large orders read as one trader, and in a thin pool they move the price on every print. There is a full method for choosing that number in how many wallets a volume bot needs, and the product overview of the console is on the Pump.fun volume bot page.
One boundary worth stating plainly: routed flow adds trading activity, it does not create lasting buyers or set a price. Rules on automated trading and marketing differ by country, this is not legal advice, and no session should be presented to buyers as something it is not.
Questions people actually ask
What is a PumpSwap volume bot?
A PumpSwap volume bot is a tool that places timed buys and sells from many separate wallets in the PumpSwap pool of a Pump.fun token, so the token keeps showing trading activity after it leaves the bonding curve. The orders settle on Solana mainnet like any other swap.
Do I need a different bot once my token migrates to PumpSwap?
No. On PumpWave the same session follows the token through the migration. Routing switches from the curve to the PumpSwap pool on its own, and the fee does not change because of it.
Can I run a session on a token that already migrated?
Yes. Paste any public Pump.fun mint and the session routes in whichever venue the token trades in now: its PumpSwap pool for current launches, or its Raydium pool for tokens that graduated before PumpSwap existed.
Does trading in the pool cost more than trading on the curve?
Both venues charge a swap fee on every trade, and a thin pool adds price movement per order. On PumpWave none of that reaches you as a separate bill: the flat 1% of target volume covers swap fees, network fees, tips, rent and wallet funding on either side of the migration.
How do I tell whether a token is on PumpSwap or Raydium?
Tokens that completed their curve after PumpSwap launched in March 2025 trade on PumpSwap; earlier graduates trade on Raydium. The console resolves the mint on chain, so you do not have to work it out before configuring a session.
Will a PumpSwap session get my token trending on DexScreener?
There is no guarantee. DexScreener weighs volume, transactions and unique makers, which a session moves, alongside liquidity, holders, visitors and reactions, which it does not. Competition in the same window decides the rest.
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.