Docs

Private token launchpad on Solana. Public chart, hidden participants.

What is plaunch

plaunch lets anyone launch a token on Solana via Raydium LaunchLab without exposing their identity. Every user gets a private wallet: a deterministic Solana Keypair derived from a single signed message on their main wallet. All launches and trades flow through the private wallet, so your main wallet never signs a transaction that touches LaunchLab.

The public chart, liquidity, and trade feed stay fully visible. The who — the wallet behind each buy, sell, and launch — does not.

Why it matters

  • MEV bots + snipers can't link your launch to your main wallet.
  • Anon whale trades don't leak your holdings graph.
  • Creator identity stays private until you choose to reveal it.

Get started (30 seconds)

  1. Connect wallet — top-right on Devnet. First connect prompts a signMessage (free, no on-chain effect). Reload never re-prompts — only actions do.
  2. Deposit anonymously — click the private-wallet chip → Deposit. Your main wallet deposits into Umbra's encrypted balance, then a relayer-submitted self-burnable stealth-pool note lands the SOL in your private wallet. No single on-chain tx links main wallet → private wallet.
  3. Trade — pick any token from the sidebar, hit Buy/Sell. Private wallet signs directly; main wallet stays inert.

Launch a token

  1. Private wallet funded → go to /launch.
  2. Fill name, symbol, description, socials, and image. IPFS pin via Pinata.
  3. Pick curve type (constant-product / linear / fixed) and migration target (AMM / CPMM).
  4. Click Launch. Private wallet signs the LaunchLab create-pool tx directly.
  5. On confirmation, plaunch persists the token to its database and redirects to the pool page.
  6. Pool creator on-chain = your private wallet. Not your main wallet.

Fees are paid by the private wallet in native SOL. LaunchLab platform fees follow the config defaults; no plaunch surcharge on top.

Privacy model

  • Deterministic private wallet — Ed25519 Keypair derived from sha512 of your main wallet's signature over a fixed message. Same wallet → same Keypair, forever.
  • Memory-only secret — the signing key lives in browser memory. Reload drops it. Only its public key is cached in localStorage for balance display.
  • Anon fund via Umbra — main wallet deposits into Umbra encrypted balance, then anon-withdraws via a self-burnable stealth-pool note to the private wallet. On-chain: two separate txs, no signer overlap.
  • Direct Raydium calls — private wallet signs LaunchLab create + buy/sell directly. No CPI wrapper, no custom program, no relayer for trades.
  • Export at any time — reveal the base58 secret from your portfolio to move the private wallet elsewhere.

What is NOT private

  • The pool chart, price, and volume are fully public.
  • Every private-wallet action is visible on-chain — only the signer identity is unlinked from your main wallet.
  • Amount + timing correlation across funding and trading is still possible with enough analysis.
  • Withdrawal to a public wallet exposes the private wallet → recipient link. Use Umbra re-deposit for anonymous exit.

Architecture at a glance

Main wallet (signMessage only) │ ▼ sha512 private-wallet Keypair (in-memory) │ ├── Umbra fund ──► shielded note ──► SOL lands in private wallet │ └── signs directly ──► Raydium LaunchLab ├─ createLaunchpad ├─ buyToken / sellToken └─ (native SystemProgram / SPL for withdrawals)

Bonding curve

Every plaunch pool uses a shared LaunchLab config on Raydium. Price follows the curve you picked at launch — constant-product (Uniswap-style), linear, or fixed. At the fund-raise target, liquidity migrates automatically to Raydium AMM or CPMM and the pool graduates. The curve locks, and the token is freely tradeable on public DEXs.

FAQ

Why does my wallet prompt to sign?

Once per session (or once per action after reload). The private-wallet secret is memory-only — reload drops it, so the first privileged action re-signs to reconstruct the Keypair. Read-only pages never prompt.

Can someone else claim my private wallet?

No. It's derived from your signature over a fixed message — reproducing the Keypair requires your wallet to sign that exact message.

What if I lose access to my main wallet?

Export the private-wallet secret (base58) from your portfolio while you still have access. Import that into any Solana wallet to keep control.

Can I use my private wallet outside plaunch?

Yes. It's a plain Solana Keypair — holds SOL + SPL, signs any tx. Export the secret key and paste it into Phantom/Backpack/Solflare.

Devnet program IDs

Clusterdevnet
RPChttps://carlina-t7pwn2-fast-devnet.helius-rpc.com
Raydium LaunchLabDRay6fNdQ5J82H7xV6uq2aV3mNrUZ1J4PgSKsWgptcm6
UmbraDSuKkyqGVGgo4QtPABfxKJKygUDACbUhirnuv63mEpAJ

Switch cluster via the pill at the bottom-right of the screen.

External

MVP · devnet · no audits · use at own risk. Bug reports welcome.
SOL