How to Create and Fund Launch Wallets for a pump.fun Bundle
Set up a dev wallet and buyer wallets for a pump.fun bundle: generating or importing keys, labels and groups, how much SOL each needs, and distributing SOL in one step.
By DevBundler Team · · 4 min read
The short answer
A bundled pump.fun launch needs one dev wallet and up to 10 buyer wallets, each funded with its buy plus about 0.003 SOL; the dev wallet needs about 0.03 SOL more plus the Jito tip and fee. In DevBundler you generate the wallets in one step, group them, and use distribute to send equal or custom SOL amounts to all of them.
Key takeaways
- Use dedicated wallets for launches, separate from the wallet where you keep your main funds.
- Each buyer wallet needs its buy plus about 0.003 SOL; the dev wallet needs about 0.03 SOL extra plus the Jito tip and platform fee.
- Label and group launch wallets so you never pick the wrong one in the launch form.
- DevBundler stores wallet keys encrypted on its server so it can sign for you. That is a custody trade-off, so keep only what you need in those wallets.
If you have ever funded eleven wallets by hand, copying addresses one by one out of a spreadsheet, you know the feeling of checking the last one and realizing you sent the dev wallet's SOL to buyer 7. This guide is about setting wallets up once, properly, so launch day is just a launch.
Which wallets you need
A bundled launch has two roles.
- The dev wallet creates the coin and makes the first buy in the same transaction. It also pays for the coin's accounts, the Jito tip and the platform fee.
- Buyer wallets buy in the same bundle, right after the dev. DevBundler supports up to 10 per launch, and the free plan allows fewer than Premium.
You do not need 10. Two or three buyers, or none at all, can be enough. Decide the number when you plan the split, then create exactly that many plus one spare.
Creating the wallets
In DevBundler's wallet manager you can generate wallets in bulk, up to hundreds at once, or import existing private keys. For a launch you usually want new ones.
- 1
Generate
Create the dev wallet and the buyer wallets in one go.
- 2
Label
Give each a name you will recognize in a dropdown, like "Dev, coin X" or "Buyer 1".
- 3
Group
Put them in a group for this launch, so you can tick the whole group in the launch form and the transfer tools.
- 4
Check balances
The manager shows live balances. New wallets start at zero.
Labels sound like housekeeping, but they are what stop you picking the wrong dev wallet under pressure. If you reuse wallets across launches, relabel them so you can tell which coin they belong to.
How much SOL each wallet needs
Every wallet needs its buy plus a small margin. The numbers:
buy + ~0.003 SOL
each buyer wallet
buy + ~0.033 SOL
dev wallet, plus tip and fee
~0.002 SOL
rent per token account, refundable
The 0.003 SOL covers the wallet's token account rent and transaction fees. The dev wallet needs the same 0.003 SOL plus about 0.03 SOL more, which pays for the coin's own accounts. On top of that, the dev wallet carries the Jito tip (we suggest starting at 0.005 SOL) and the platform fee shown at confirmation. If this is your account's first launch, there is also a one-time lookup table setup of about 0.005 SOL.
For DevBundler's default setup of 1 SOL dev and 0.5 SOL per buyer:
| Wallet | Buy | Fund with at least |
|---|---|---|
| Dev | 1 SOL | 1.038 SOL plus platform fee |
| Buyer 1 | 0.5 SOL | 0.503 SOL |
| Buyer 2 | 0.5 SOL | 0.503 SOL |
| Buyer 3 | 0.5 SOL | 0.503 SOL |
Round those up. A wallet funded to the exact amount turns red the moment you raise the tip or the priority fee, and a red wallet blocks the launch. How much SOL to launch on pump.fun has more worked budgets.
Funding them in one step
Instead of sending to each address by hand, use distribute.
Source wallet
one wallet holds the total launch budget
Distribute
pick the group, set equal or custom amounts
Launch wallets
each receives its buy plus margin
Launch table
shows every wallet's balance and what it still needs
Distribute sends SOL from one wallet to many, with either the same amount for each or a custom amount per wallet. You can send it all now. Premium can also schedule a distribution to go out over time on an interval. For a launch, sending now and checking the launch table afterwards is the simple path.
The custody trade-off
DevBundler is a hosted app. When you generate or import wallets, their private keys are stored on DevBundler's server, encrypted with AES-256-GCM using a key derived from your password (argon2id) plus a server secret. The server uses them to sign launches and trades, which is what makes one-click launches and multi-wallet trading fast.
That is a real trade-off and worth being clear about. You are trusting DevBundler's server with the keys of the wallets you use in it. Some practical consequences:
Wallet hygiene for hosted launch wallets
- Use a strong account password, at least 12 characters, and do not reuse it.
- Fund launch wallets for the launch, not as storage.
- Sweep profits to a wallet you control outside the app when you are done.
- Export keys only when you need them. Export asks for your password again and shows the key for 10 seconds.
- Let the session auto-lock; do not leave a logged-in tab open on a shared machine.
After the launch: getting SOL back
When you are finished with a coin, consolidate. It sweeps the chosen wallets back into one, optionally keeping enough for rent or closing token accounts so the roughly 0.002 SOL rent in each comes back too. With eleven wallets, that rent adds up to something worth recovering.
Then move what you want to keep out of the app entirely. With funded, labeled wallets ready, the next step is the launch itself: how to launch a pump.fun coin with a bundle.
Frequently asked questions
›How many wallets do I need for a pump.fun bundle?
One dev wallet plus however many buyer wallets you want in the bundle, up to 10 in DevBundler. The free plan allows fewer wallets per bundle than Premium.
›How much SOL should I put in each launch wallet?
Its planned buy plus about 0.003 SOL for its token account and fees. The dev wallet needs about 0.03 SOL more for the coin's accounts, plus the Jito tip and the platform fee.
›Can I use my existing Phantom or Solflare wallet?
You can import an existing private key into DevBundler, but it is better to use fresh wallets just for launches, so your main funds are never in a wallet whose key is stored on a server.
›How do I get SOL back out of launch wallets?
Use consolidate in DevBundler to sweep wallets back into one, optionally closing token accounts to recover their rent of about 0.002 SOL each.
Keep reading
How to Keep Your pump.fun Launch Wallets Safe
Practical wallet safety for pump.fun launches: separate your main wallet, fund only what a launch needs, sweep profits out and lock down the account you launch from.
· 5 min read
How DevBundler Stores Wallet Keys (and What That Means for You)
A plain explanation of DevBundler's custodial key model: how keys are encrypted, why the server signs for you, and how to limit what you trust it with.
· 4 min read
Consolidating SOL From Many Wallets After a Launch
How to sweep SOL from your launch wallets back into one: what to sell first, closing token accounts to reclaim rent, and the order that avoids stuck dust.
· 4 min read