Launching on Pons
launchAndBuy
The launch is a single atomic transaction on the Pons router: it deploys the token, creates its bonding curve, and buys the opening position in one go. There is no separate "create then buy" flow — if any step reverts, nothing happens.
TokenParams carries: name, symbol, logo URL, description, creator fee recipient, opening buy amount, and snipeTaxExemptions[].
Through Bundle
The wizard collects name/ticker/description/image, then the engine:
- Checks
canLaunch(deployer)— refuses early if the wallet isn't whitelisted - Reads
launchFee+ launch economics from the factory - Fills
snipeTaxExemptionswith the bundle wallets (max 32 — the reason a bundle stays under 32) - Runs an
eth_callsimulation of the exact calldata - Broadcasts
launchAndBuyfrom vault wallet 0 only if the simulation succeeds
The deployer needs enough ETH for launchFee + opening buy + gas — the simulation catches an underfunded wallet before a transaction exists.
Image
The dropzone preview is local. To put art on-chain, paste a hosted image URL — it goes into the logo field of TokenParams. Pons has no public upload endpoint (the API 401s), so a local file stays on your machine and still displays in Live.
Solo launch
The Setup view's solo link runs the identical transaction from your connected wallet instead of the vault — same canLaunch check and simulation, no bundle exemptions. It's a real Pons launch, just a single-wallet one.