pump.fun bundles

Normally a degen.zone launch creates your token on our market. pump.fun mode does not: it is a mode of the Solana venue that creates the token on pump.fun’s own program and curve, then executes a bundle - your first buy plus other wallets buying in the same slot, so nobody can snipe the gap between “token created” and “first buys landed”.

It exists on Solana only - there is no pump.fun on any EVM chain - and it carries none of degen.zone’s own machinery: no reward model, no fee routing, no LP earnings, no cross-chain expansion. Your token lives and trades on pump.fun.

These are read straight from the launch code - earlier write-ups had them wrong:

Bundle fee

0.1 SOL flat

Buy wallets

up to 19

Delivery

one transaction, then any overflow next block

Atomicity

create + the first buys in ONE transaction

Quote

SOL, or a token from pump.fun’s roster

Curve

pump.fun’s own

• The fee is a flat 0.1 SOL, paid once, in the launch transaction - not a percentage. That is degen.zone’s entire take on this venue.
• Up to 19 buy wallets. The launch itself is ONE transaction: create_v2 + the flat fee + as many buys as that transaction measurably holds, all against the token it just created. Nothing can land between them, because there is no between. How many fit is measured per launch, not assumed - a Solana transaction is bounded three ways at once (1232 bytes, 64 instructions counting every inner call, and the compute limit) and a paired launch spends far more of all three than a SOL one. In practice that is your dev buy plus one or two wallets.
• Any remaining wallets buy the next block, as lookup-table transactions sent normally. Those carry a brief one-block gap a sniper could act in - stated here, not discovered at signing - and the table they use is yours: its rent is reclaimable from the launch page once the chain lets it go.
• The quote is SOL by default, and may instead be a token from pump.fun’s own quote roster (a paired launch). A pair is a different curve in a different unit, so the opening buy is sized in that token, not in SOL.

The create and its first buys are one transaction. A Solana transaction either executes whole or does nothing at all, so those buys cannot be separated from the creation they follow: a sniper has no slot to act in, because there is no between. No relay, no auction, no third party - the guarantee is the runtime’s own.

It is the same primitive that makes hidden bundles dangerous elsewhere; here it is pointed at snipers and paired with full disclosure. Wallets past what one transaction holds buy the next block instead, and that gap is stated above rather than implied away.

There are three wallet sources for the bundle, all of them disclosed and non-custodial:

• Generate - throwaway keypairs made in your browser; you fund them from your own wallet in one transfer and they buy alongside your first buy.
• Use my own - you paste one private key per row; each wallet buys with the SOL it already holds (no fan-out to fresh wallets for a scanner to flag).
• One buyer - you paste ONE deployer key plus up to 30 recipient addresses (never keys). The deployer buys the whole amount in the bundle, then sends each recipient its share in plain, public transfers over the next blocks. An optional dev buy lets the deployer keep a configurable amount for itself (any SOL, or any % of supply) and distribute only the recipient amounts.

Whichever source you use, before launch:

• you must export their keys - a mandatory download - so you, and only you, control them;
• you fund them from your own wallet in one transfer; they sign their buys locally;
• degen.zone never sees or holds a key, and does not manage the wallets after launch - selling or moving them is yours to run in your own tooling.

Optionally, your token’s mint can end in a chosen string - the classic …pump suffix, just like pump.fun’s own tokens. Because the bundle already mints the token client-side, the address is found by a browser-side grind (generate keypairs until one matches). A four-character suffix like pump is the practical browser limit; longer patterns grow exponentially. It is off by default. Same idea as EVM’s salt grind - the shared mechanics are in Vanity addresses.

After launch, the fees on your token are pump.fun’s. Its curve charges a protocol fee plus a creator fee that scales with market cap (read live from the curve - around 1% early). None of degen.zone’s fee models exist on this venue. Our entire take is the flat 0.1 SOL bundle fee, paid once at launch.

Live - live on Solana mainnet. Both shapes have been launched for real: a SOL-quoted coin whose create and buys landed in a single transaction in one slot, and a coin quoted in a token from pump.fun’s roster, whose overflow buys landed the block after. Both were sold off and closed out afterwards.

What a real launch taught us is in the numbers above: the transaction’s capacity is measured before anything is funded, and a launch that will not fit is refused with a sentence rather than attempted with your fee already spent.

In-app trading covers both. A SOL-quoted coin buys and sells in SOL; a paired coin buys and sells in its own token, with every figure on the trade panel - the balance, the quick amounts, the quote and the minimum after slippage - denominated in that token and labelled with its ticker. The network fee is still SOL, which the panel says when it matters.