Skip to main content

​
token launch

full launch pipeline on pump.fun. token creation, dev buy, and bundle buys all land atomically in the same block via jito. nobody frontruns you. the contract address is available before the token goes live.

​
the pipeline

pre-launch:   reserve CA → upload metadata → prefund wallets
block 0:      create token + dev buy + bundle wave 1     (atomic jito bundle)
block 1-N:    bundle wave 2, 3...                        (delayed waves, different blocks)
block 1+:     snipe wallets fire                         (block-targeted, independent txs)
post-launch:  swarm buys hit                             (parallel, dozens of wallets)
continuous:   volume bot starts                          (automated buy/sell cycles)
              regular buys fire                          (standard buys, no jito)
every phase is optional. run a bare launch with just a dev buy, or go full send with all phases enabled.

​
early contract address

call reserve_mint to generate a vanity address ending in pump before you launch. this gives you the CA upfront — share it in telegram groups, post it on twitter, build hype before the token even exists on-chain. the reserved address is locked to your account. pass it to launch_token when you’re ready. if you don’t reserve one, a random address is assigned at launch.

​
token metadata

set in the launch modal:
fieldnotes
nametoken display name
tickersymbol (e.g., GANK)
descriptionshows on pump.fun
imageuploaded to ipfs automatically
twitteroptional social link
telegramoptional social link
websiteoptional social link
metadata is immutable once launched. double-check before you send it.

​
dev buy

the dev buy is atomic with token creation — same jito bundle, same block. set dev_buy_sol to however much sol you want in. the dev wallet must be a dev type wallet. this wallet also collects creator fees.

​
prefunding

before launch, the system checks every wallet that needs sol (bundle, snipe, swarm, volume) and automatically prefunds them from the dev wallet. it only sends the shortfall — if a wallet already has enough, it skips it. this means you only need to fund your dev wallet. everything else is handled.

​
execution

hit launch. the engine:
  1. uploads metadata to ipfs
  2. prefunds all child wallets from dev
  3. builds the jito bundle (create + dev buy + bundle buys)
  4. submits to jito and waits for confirmation
  5. fires snipe wallets at their target blocks
  6. fires swarm buys in parallel
  7. starts volume bot
  8. fires regular buys
the live feed shows every transaction as it lands.

​
jito tip

the jito tip determines bundle priority. default is 0.0001 sol. increase it during high congestion for faster inclusion.

​
launch phases

each phase is a separate module. see the dedicated pages:

bundles

atomic block 0 buys + delayed waves for later blocks

sniping

block-targeted buys starting from block 1

swarm

parallel buys from dozens of prefunded wallets

volume bot

automated buy/sell cycles post-launch

regular buys

standard buys after launch, no jito

vamp

stop everything, sell, recover all sol