Launch setup

A coin in Apache has one page for its whole life. While it's a draft, that page is its setup: the token, the dev wallet, who buys at the opening and how fast. Start turns the same page into the coin's panel, and only Launch on Pump.fun on that panel sends anything on chain. Until then you can change everything, as a team, without spending a lamport.

A coin's life

Launch coin in the main menu makes a fresh draft and opens its page, so the address never changes while you work. Everything saves a moment after you change it (Saving…, then Saved), and teammates on the same draft follow along. If someone saved over you, a bar says A teammate saved changes to this draft and offers Load their version.

1. Draft: the setup. Find it later under Drafts, or reuse it with Save template and Clone draft in the sidebar.
2. Ready: after Start. The panel is open, the book shows the curve as the opening will leave it, nothing is on chain. Edit setup takes it back to a draft.
3. Launching: after Launch on Pump.fun (Queued for the few seconds until the server picks it up). The server creates the token, sends the bundle, then the start buys.
4. Live: the coin trades on the panel. A Migrated badge appears once the curve completes and it moves to PumpSwap. If something needs a look the launch stops at Paused.

The setup, step by step

The steps sit in a row at the top (Coin, Dev, Buyers, Funding, Execution, Exit plan, Handshakes) with Back and Next under each. The sidebar on the right, where Panic sell will be later, holds Start, the checklist and the numbers of the opening, so you always see what your choices add up to.

1. Coin

ImagePNG, JPEG, WebP · 400 KB

Drop it or click to pick. It's stored with the coin and served to every wallet and explorer once the coin exists.

Name · Ticker32 · 13 bytes

The limits are bytes, not letters, so an emoji takes several. The ticker is uppercased and loses its spaces.

Descriptionup to 2,000 characters

Shows on Pump.fun and in wallets. The How it shows preview renders it next to the name.

Website · X · Telegramhttps links

Optional links in the token's metadata.

Internal name, never shown on chain

A label for your team, used in lists and the dashboard.

2. Dev

The Dev wallet creates the coin, pays for it and makes the dev buy; its address shows as the creator on Pump.fun. Pick one of your dev wallets, make one with New dev, or Import yours. A wallet that already launched a coin carries a warning, since a fresh dev looks cleaner.

Dev buy in · SOLNone, 0.25, 0.5, 1, 2, 3

The first buy of the coin, inside the creation transaction itself. Type any amount, or pick a preset.

Dev buy in · % supply1, 2, 3, 5, 10, 15

Type the share instead. It's saved as the SOL that takes it at the opening, Pump's fee included, and quoted again from the chain when the launch signs. One buy can take at most 79.3% before the curve completes.

Under the presets you see Takes of supply, Dev wallet needs and It has (cached). When the dev is short, a button sends the difference from the main wallet.

3. Buyers

Your buyer wallets show as squares (or a List): brighter means more SOL, a yellow dot means Warmed up. Narrow them with a folder (and Subfolders), a search by Label or address, and the chips Warmed up, Never launched, Has SOL and Free only. Then work in two moves:

1. 1
   Select

   Drag a box over the squares (shift or ⌘ adds, shift click picks a run), or use All, None, Invert, or Pick N at random or from the top among the free wallets that match the filters.

2. 2
   Add the selection to a group

   Jito bundle buys in the creation block, all or nothing, and holds four. Start buys go one transaction each right after the creation, up to 1,000: all at once or one by one (see Execution). Take N out of the launch removes them again.

Each group has one amount setting, Each buys: Same for all, or Random between a From and a To. Shuffle the order mixes the start buy queue (it matters one by one; all at once, whoever lands first buys first). Every row shows Needs X SOL with fees and rent. A wallet sits in one group only, and the dev can't also be a buyer.

4. Funding

Balances lists every wallet of the opening with its group, what it buys, what it needs and what it has, from the balance cache (up to a minute old). Top up counts Wallets short and SOL missing, and its buttons open the normal Fund review for exactly the short wallets of a group, by any route. This step is optional now: Start works with wallets short, Launch doesn't. See Fund, collect and reclaim.

5. Execution

SpeedFast · Turbo · Ultra

Presets for the Jito tip and the priority fee: Fast 0.0005 / 0.0005 SOL for quiet hours, Turbo 0.002 / 0.001 for most launches, Ultra 0.01 / 0.003 for a busy network.

Jito tip, SOLdefault 0.0001

Buys the bundle its place in the block. Each start buy carries its own tip too, plus 0.00001 SOL to Helius Sender so that route takes it.

Priority fee, SOL per txdefault 0.0001

Paid by every transaction of the launch.

Slippage, %default 5 · 0.1 to 50

Lowers the tokens a buy accepts. It never spends more SOL than the buy's amount.

Start buysAll at once · One by one

All at once (the default) works like the ApeSync sniper: the worker watches for the creation, and the moment it shows up on chain, before it even confirms, signs every start buy in one pass and sends them together through Jito, Helius Sender and the RPC, again every few hundred milliseconds until each one lands or expires. Most land in the next block or two after the creation, in no set order. Since they race, each one's minimum is quoted as if all the others bought first, less your slippage, and it spends exactly its amount: a wallet that lands early just gets more tokens. One by one starts once the creation confirms and sends them in your order with Pause between start buys, ms (1 to 60,000) between them, which reads less like a bundle on the trackers.

6 and 7. Exit plan and Handshakes

Both optional. An exit plan set here arms the moment the coin is created (Exit plan and auto sell). Prepared handshakes wait on the panel to be loaded in one click (Handshakes). Neither sends anything at Start.

The opening

The sidebar's The opening adds it all up, and the ready panel shows the same numbers. A bar under it splits the supply you take between the dev (violet), the bundle (red) and the start buys (green).

Dev buy · Jito bundle · Start buys

SOL each part spends and the share of supply it takes.

We take of supply

The total share the opening buys.

Market cap after

Where the market cap stands, in SOL, once every opening buy has landed.

Fees and tips

Priority fees and Jito tips of every transaction.

Platform fee 1.5%

Apache's fee on the buys (Fees).

Wallets need, all in

Everything the wallets must hold: buys, fees, tips, the platform fee, plus a reserve for rent (0.03 SOL for the dev, 0.003 SOL per buyer).

Start

The checklist ticks off Name and ticker, Image, Dev wallet, the buyers, funding (Every wallet funded, or N wallets short of SOL: fund before Launch) and the exit plan. Only the first three are required, plus one rule: buys that would complete the bonding curve are refused (These buys would finish the bonding curve. Buy less.).

Start opens the coin's panel with the star animation. Nothing is sent: on the ready panel, Launch on Pump.fun stands where Panic sell will be, next to the opening's wallets with what each needs and has, Read balances now, the exit plan, and Edit setup, Clone and Save as template.

Launch on Pump.fun

The dialog Launch $X on Pump.fun says it plainly: your wallets sign the creation and the buys for real, and none of it can be undone. It lists what happens, then reads every wallet's balance live (Wallets checked, Short of SOL). A short wallet blocks the launch with Top them up first. With everything funded, type the ticker in Type X to launch and press Launch $X.

1. The token is created with the dev buy and the bundle's buys, in one Jito bundle: one block, all or nothing.
2. The start buys follow, one transaction each: all at once the moment the coin exists, or one by one in your order with your pause.
3. Trading opens on the panel as soon as the coin exists.

While it launches

The panel shows Creating the token and the bundle, a count of settled steps and the Launch log tab with every transaction. It runs on the server: closing the tab doesn't stop it.

Once the creation lands, the log says where each start buy landed in blocks after it: same block, +1 block, +2 blocks, with a line on top that counts them, for example Start buys landed: 15 of 15 · +1 block · 12 · +2 blocks · 3. The admin Telegram post that announces the coin carries the same count.

• The bundle is never sent twice. If it expires with nothing on chain and no token at its address, it's built again with a fresh blockhash, three attempts in all. Then the launch pauses and Resume launch asks for another try.
• A failed start buy doesn't stop the rest. It's written in the launch log and the launch moves to the next buyer; that wallet can still buy from the panel.
• Pause launch stops whatever hasn't been sent yet; a transaction already out can still land. The coin's creator or a workspace owner or admin can pause and resume.