pump.fun bundles

Normally a Degenland 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 a few 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 Degenland’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 (across two bundles)

Bundles

atomic + next-block

Atomicity

create + first buys in one Jito bundle

Quote

SOL (fixed)

Curve

pump.fun’s own

• The fee is a flat 0.1 SOL, paid once, inside the bundle - not a percentage. That is Degenland’s entire take on this venue.
• Up to 19 buy wallets, across two bundles. The first is an atomic Jito bundle: create_v2 + the flat fee + tip, plus up to 4 buys (including your dev buy) that reference the just-created token directly - nobody snipes between create and those buys. A second bundle the next block adds up to 15 more buys (v0 transactions with address lookup tables, a few per transaction), for 19 total. The later 15 carry a brief one-block gap a sniper could act in - stated here, not discovered at signing.
• The quote is SOL, fixed by pump.fun; there is no pair or fee-model choice on this mode.

The buys are submitted as a single Jito bundle: all of its transactions land in one block, in order, or none of them do. That is what makes the launch fair to you - a sniper cannot slot a buy between the token’s creation and your bundle’s buys, because there is no between. It is the same primitive that makes hidden bundles dangerous elsewhere; here it is pointed at snipers and paired with full disclosure.

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;
• Degenland 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 Degenland’s fee models exist on this venue. Our entire take is the flat 0.1 SOL bundle fee, paid once at launch.

Built · not live - built, not switched on. The chain path (create then sequential buys against pump.fun’s program) is written and proven on a devnet lifecycle run with quotes exact to the digit. The launch form shows the mode inert, with its reason. Three things gate the flip:

• a small watched mainnet bundle run. Jito runs no block engine on devnet, so the atomic bundle itself can only be proven where one exists - a throwaway mainnet launch that costs ~1-2 SOL all-in. It is the one venue we deploy nothing new for, because pump.fun is already on mainnet;
• client sign-off on the posture. This is a brand call, not an engineering one: bundled pump.fun launches sit next to rug tooling in most people’s minds, carry none of Degenland’s differentiators, and earn only the flat fee. Disclosed-only is the non-negotiable floor.

When those land, flipping one flag is the only change on this surface.