BTC:
ETH:
SOL:
BNB:
XRP:
Launch playbook

How to launch on Solana with Pump.fun

A mechanical walkthrough of the Solana rail: what you fill in, what gets simulated, what you sign, and what a green confirmation actually means.

8 min readReviewed July 18, 2026Launch playbook

The short answer

Open /launch, keep the Solana rail selected, choose a profile (Standard is the default), add name / ticker / artwork, optionally set a disclosed creator buy, connect a Solana wallet, and press launch. The app uploads metadata, simulates the Pump.fun create, asks for a signature, then waits for confirmation and writes a local receipt.

Before you open Launch

  • Browser wallet with Solana support (Phantom, Solflare, Backpack, or MetaMask Solana).
  • Enough SOL for create fees, any disclosed buy, and—on mainnet—platform fee and tip.
  • Square artwork (PNG, JPG, GIF, or WEBP) under the size limit shown in the UI.
  • Clear name and ticker rules: letters/numbers for ticker; no assumption that the ticker is unique worldwide.

The launch path, in order

  1. Select Solana. The rail switcher always shows Solana, Robinhood, and Ethereum. Solana and Robinhood are live; Ethereum is locked.
  2. Pick a profile. Standard (one creator path), CTO / Fair (no creator buy), or Team (disclosed multi-wallet buys). Details live in launch profiles and strategies.
  3. Coin details. Name, ticker, description, artwork. Social links are optional but should be real HTTPS URLs if you fill them.
  4. Optional developer buy. On Standard, a buy can land in the same launch transaction. Zero is valid. Anything you disclose should match the story you tell the market.
  5. Connect wallet. The connected address becomes the default fee recipient / creator buy wallet where empty fields need filling.
  6. Launch. Metadata upload → simulation → wallet signature → confirmation. Read the simulation failure text if the button stops early.
  7. Save the receipt. Local receipt stores mint, signature, and network. Signed-in users can also push a verified server backup—see receipts and evidence.

Devnet vs mainnet

Devnet is the default for product development and practice: no Trenchables platform fee, no Jito path. Mainnet uses the same UI button but requires production configuration (RPC, fee recipient, Jito tip settings). On mainnet the create (and optional buy) can travel with settlement in an atomic Jito bundle so fee and tip either land with the create or not at all.

If the header says Mainnet and you expected Devnet—or the reverse—stop. Wrong network is the most expensive “UI looks fine” mistake.

After a successful create

Confirm the mint on a Solana explorer. Treat the mint address—not the ticker—as identity. Bonding-curve mechanics still apply; see bonding curves and launches and Pump.fun and PumpSwap for the market side after create.

Primary and official sources

Next

Pick the right profile before you fill the form.