How to Sell a pump.fun Coin Across Multiple Wallets

You launched with a dev wallet and six buyers. The coin is up, and now the tokens are spread across seven wallets. Selling them one at a time in a normal wallet app means seven imports, seven swaps and seven chances to fat-finger an amount while the price moves.

The short answer: pick the wallets, pick a percentage, and let a tool send one sell per wallet, quoted in the order they will land. Then sweep the SOL home. The rest of this post is about doing each of those well.

#What does "selling across wallets" actually involve?

On Solana, a wallet can only sell tokens it holds, and only with its own signature. There is no single "sell my position" button that reaches into other wallets. So a multi-wallet sell is really a batch of separate sells, one per wallet, each signed by that wallet's key.

That has two consequences. First, whatever tool you use needs to be able to sign for every wallet in the batch. Second, the sells interact with each other, because they all trade against the same bonding curve (or the same PumpSwap pool after migration). Each one moves the price before the next one arrives.

In DevBundler, the server holds the encrypted keys of the wallets you created or imported and signs for them, which is what makes a one-click batch possible. That is a custodial trade-off, and it is worth keeping only the SOL and tokens you need in those wallets.

#Step by step in DevBundler

1. 1

   Open the coin's dashboard

   Every launch has a project page with holdings, profit and the chart. Your wallets for that coin are listed with their token balances.

2. 2

   Tick the wallets

   Pick specific ones or tick All. Wallets with no tokens of this coin have nothing to sell.

3. 3

   Choose an amount

   Press a sell preset (a percentage of each wallet's tokens) or type a custom percentage. Presets are editable, so set them to the steps you actually use.

4. 4

   Pick Fast or Bundle

   On mainnet, Fast sends each wallet's sell on its own; Bundle (Premium) packs them into one Jito bundle.

5. 5

   Confirm

   The fee is shown before you confirm. After sending, the trade history and profit numbers update per wallet.

There are keyboard shortcuts for the trading bar too, which helps when you are watching the chart and do not want to reach for the mouse.

#Percentage or token amount?

Launch wallets rarely hold the same amount. If you bought by SOL, later wallets got fewer tokens than earlier ones, because each buy paid a higher price on the curve. If you bought by percentage, the amounts are close but not equal.

Selling by percentage of each wallet's holdings sidesteps all of that. "Sell 25%" means a quarter of whatever each wallet holds. It keeps the wallets proportional, it never asks a wallet to sell more than it owns, and it maps cleanly onto an exit plan written in percentages. If you have not written one, planning your exit on a meme coin is a framework for that.

#Fast mode or Bundle mode?

Neither is better in every case. Fast is simple and forgiving: a single bad wallet does not hold up the rest. Bundle gives you tight timing and all-or-nothing behavior, which matters if you want the sells to land together rather than having outside trades slip in between them. The trade-off is that one failing transaction takes the whole bundle down with it.

Speed presets (Normal, Fast and Turbo, with Turbo on Premium) set the priority fee. If the network is busy and sells are slow to land, raising the speed helps. Solana priority fees explained covers what you are paying for.

#Why the order of sells matters

Here is the part that trips people up. Suppose five wallets each sell 50%. If the tool quotes all five against the current price, the first sell lands and drops the price. The second wallet's quote assumed the old, higher price, so its minimum SOL out is now too high. It fails slippage. So do the third, fourth and fifth.

DevBundler quotes every wallet in a batch in the order it will be sent, each one against the price left by the ones before it. That keeps every wallet's slippage minimum reachable. The full story, including the error codes you will see if this goes wrong, is in why batch sells fail.

#After the sell: get your SOL back in one place

Once the sells land, the SOL sits in each wallet. Leaving it scattered is how people lose track of profit, and it is also more exposure than you need in wallets whose keys live on a server.

Use consolidate to sweep the wallets back into one. You can keep a little SOL in each for rent, or close the token accounts you are done with. Each token account holds about 0.002 SOL of rent that comes back when it is closed. Across ten wallets that is roughly 0.02 SOL, small but not nothing, and it is yours. Then move what you want to keep to a wallet you control yourself.

#Common mistakes

• Ticking All and forgetting a wallet you meant to hold. Check the selection before you confirm.
• Leaving no SOL for fees. A wallet needs a small amount of SOL to pay for its own sell transaction.
• Using Bundle mode with a wallet that is likely to fail, which sinks the whole bundle.
• Selling after the curve completed using an old tool that still targets the curve. DevBundler switches to PumpSwap automatically, but other setups may not.