Step 6 · Launch on Pons

Only reachable once steps 1–5 are complete — enforced in-page: the gate is recomputed from vault existence, the wallet-0 balance, and the plan's confirmed-entry count, and New Launch stays locked until all of it is genuinely true.

The wizard

New Launch unlocks and opens the launch wizard: token name, ticker, description, and image (drag-and-drop preview or a hosted URL — files stay local, URLs go on-chain in the logo field).

On deploy, the app sends a single launchAndBuy transaction signed by vault wallet 0:

• Creates the token + bonding curve atomically
• Executes your opening buy in the same transaction
• Passes the bundle wallets as snipeTaxExemptions (Pons caps this at 32) so the progressive buys never pay the opening snipe tax

Before broadcasting, the app runs canLaunch(deployer) and an eth_call simulation of the exact calldata — a revert means a clean error, never a burned transaction.

Whitelist

Pons public launching is whitelist-gated. If canLaunch(your deployer) is false the wizard says so up front — you will not get through setup to discover it at the end.

Solo mode

The solo launch link at the bottom of Setup bypasses the bundle pipeline entirely: the wizard opens without the steps 1–5 gate, launchAndBuy is still signed by vault wallet 0, but no bundle wallets are passed as exemptions. Same simulation and whitelist checks. Honest label, deliberate escape hatch — not the default path.

After launch

The app auto-tracks the new token in Live. Step 7–8 controls become available there.