How to Split Supply Across Bundle Wallets on pump.fun
Equal SOL or equal percent? How to split a pump.fun launch across your dev and buyer wallets, why order matters on the bonding curve, and how to set a total share cap.
By DevBundler Team · · 5 min read
The short answer
Start from the total share of supply all your wallets will hold, then divide it. Equal SOL per wallet gives later wallets slightly fewer tokens; equal percent costs later wallets slightly more SOL. In a real mainnet quote, a 3% dev buy plus three 2% buyers cost 0.8711, 0.6092, 0.6335 and 0.6592 SOL for 9% in total.
Key takeaways
- Decide the combined share first. The per-wallet split comes second.
- Equal SOL buys give each later wallet fewer tokens, because every buy raises the curve price.
- Equal percentage targets cost each later wallet more SOL, but every wallet ends up with the same share.
- Wallets are filled in send order, so the order you set changes what each one pays.
- DevBundler blocks any split that would sell out the whole bonding curve in the launch.
The question to ask first is not "how much should each wallet buy". It is "how much of this coin do I want my wallets to hold, all together, when the launch block lands". Get that number right and the split per wallet is easy. Get it wrong and no split will save it.
Step one: set a combined ceiling
Every pump.fun coin has 1,000,000,000 tokens. Every wallet that buys in your bundle bought in the same block as the create, so your combined share is the number that matters to buyers.
Pick a ceiling you are comfortable with. A useful reference: in a real quote on a fresh mainnet curve, a 1 SOL dev buy plus three buyers at 0.5 SOL each held about 8.18% of supply together. That is DevBundler's default setup. A bundle that holds several times that share is a very different coin from a buyer's point of view.
Step two: choose how to divide it
Once you have a ceiling, there are two basic ways to fill it.
Equal SOL vs equal percentage
| Equal SOL per buyer | Equal % per buyer | |
|---|---|---|
| What you set | 0.5 SOL each, for example | 2% each, for example |
| What changes per wallet | tokens received | SOL spent |
| First buyer vs last | first gets the most tokens | last pays the most SOL |
| Easy to budget | yes, it is a fixed number | close, the app shows the SOL |
| Holdings look | slightly uneven | identical |
Here is the equal-percentage case from a real DevBundler quote:
| Wallet | Target | SOL needed |
|---|---|---|
| Dev | 3% | 0.8711 |
| Buyer 1 | 2% | 0.6092 |
| Buyer 2 | 2% | 0.6335 |
| Buyer 3 | 2% | 0.6592 |
Same 2% each, but buyer 3 pays about 0.05 SOL more than buyer 1. Total: 9% of supply, curve about 11% sold.
With equal SOL, the effect runs the other way. Each buyer spends 0.5 SOL, but the first buyer's 0.5 SOL gets more tokens than the third's. The gap is small with a few wallets and grows the further up the curve you go. Why later bundle wallets get fewer tokens shows the curve math.
Why order matters
A Jito bundle executes its transactions in order, and the buys inside them run in order too. So the wallet you put first is the one that buys at the lowest price after the dev.
Create
the coin starts at about 28 SOL market cap
Dev buy
first and cheapest buy on the curve
Buyer 1
pays slightly more per token than the dev
Buyer 2 to 10
each pays a little more than the last
This is why DevBundler quotes every wallet after the ones before it, in send order. The estimated share in the launch table is what that wallet will get at its position in the queue, not what it would get if it bought first. If you reorder wallets, the estimates change.
Four common split patterns
Different devs want different shapes. None of these is a recommendation for a specific coin; they are starting points to adjust in the launch table.
Dev-heavy. A larger dev buy, small buyer buys. The dev wallet is clearly the main holder and the buyers are a small top-up. The result is a dev with a stake and not much else. How to choose your dev buy size helps you set that first number.
Flat. The dev and buyers all target about the same share. No single wallet stands out, though the combined total is the same.
Default. DevBundler's suggested 1 SOL dev and 0.5 SOL per buyer. The dev ends up with roughly twice what each buyer gets.
Few and small. Two or three buyers at modest amounts. This keeps the combined share low and the cost down. Remember each wallet still needs about 0.003 SOL of overhead, so many tiny buys is less efficient than a few small ones.
The curve has a ceiling too
pump.fun's bonding curve sells 79.31% of supply before it completes and the coin migrates to PumpSwap. If your launch buys added up to that, the coin would complete in the launch block, and any buy that came after would fail with error 6005, BondingCurveComplete.
DevBundler blocks a launch whose buys would sell out the whole curve, so you cannot do this by accident on mainnet. You can get close to it on devnet without trying, though: devnet's pump.fun curve is configured very differently, and in testing a single 1 SOL dev buy took 82% of supply and completed the curve. Do not use devnet percentages to plan a mainnet split.
Setting it up in DevBundler
- 1
Pick the dev wallet and buyers
Up to 10 buyers. The free plan allows fewer per bundle than Premium.
- 2
Choose SOL or percent
Set the buys as SOL amounts or as a percentage of supply.
- 3
Same for all, or custom
Set one value for every buyer, or type a different amount per wallet.
- 4
Read the share column
Each row shows the estimated share at that wallet's position in the send order, plus the SOL it needs.
- 5
Check the combined total
Compare it with your ceiling. If it is over, trim the largest buys first.
The table also flags any wallet that does not hold enough SOL for its buy plus about 0.003 SOL, and the dev wallet's extra 0.03 SOL plus tip and fee. Red rows block the launch until fixed.
Before you commit
Write down three numbers: the combined share, the dev's share, and the total SOL. If any of them surprises you when you see them on paper, change the split now. Then run the full launch through the steps in how to launch a pump.fun coin with a bundle.
Frequently asked questions
›How should I split supply between bundle wallets?
Decide the total share you want all your wallets to hold, then split it either by equal SOL per wallet or by equal percentage per wallet. Equal percentage makes every wallet's share identical; equal SOL is simpler to budget.
›Why does my last bundle wallet get fewer tokens?
Each buy moves the bonding curve price up, so the next wallet pays a higher price. With equal SOL buys, the first wallet gets the most tokens and the last gets the fewest.
›What total supply share is too much for a bundle?
There is no official limit. The larger the combined share, the more likely traders are to treat the coin as a dump risk and skip it.
›Can a bundle buy out the whole bonding curve?
In principle a large enough set of buys could, but DevBundler blocks any launch whose buys would sell out the whole curve. The curve completes after 79.31% of supply is sold.
Keep reading
Why Later Bundle Wallets Get Fewer Tokens on pump.fun
In a pump.fun bundle, equal SOL buys get fewer tokens with each wallet. Why the bonding curve does this, real numbers for 4 and 11 wallets, and how to plan around it.
· 4 min read
How to Choose Your Dev Buy Size on pump.fun
How big should your pump.fun dev buy be? What 0.5, 1 and 2 SOL get you on a fresh curve, what buyers read into it, and how to pick a size you can defend.
· 5 min read
How Much SOL Do You Need to Launch on pump.fun?
How much SOL a pump.fun launch really costs: the buys, about 0.003 SOL per wallet, 0.03 SOL for the dev wallet, the Jito tip and fees, with three worked budgets.
· 5 min read