Docs
SPAWNPAD // DOCUMENTATION

How SpawnPad works.

In plain language, with the receipts.

01 / VANITY

The mandatory Spw mint

Every token launched through SpawnPad uses a real Solana keypair whose public address ends in the exact case-sensitive characters Spw. The keypair is ground in your browser with your device's WebCrypto — the private key never leaves your browser. The mint address is never faked, shortened, or decorated: it is the actual mint account created on-chain.

A 3-character Base58 suffix has a search space of 58³ ≈ 195,112 — expect a grind of seconds to minutes depending on your CPU and worker count. Generation is never guaranteed to finish in any particular time, and can be cancelled at any point.

02 / ENGINE

Pump.fun integration

SpawnPad launches through the official pump.fun program 6EF8rrecthR5Dkzon8Nwu78hRvfCKubJ14M5uBEwF6P using its create_v2 instruction, which accepts a caller-supplied mint keypair that co-signs the launch transaction. This is the same mechanism pump.fun's own frontend uses to grind its pump suffix.

Trading happens on pump.fun's bonding curve (virtual reserves, 1% protocol fee). When a curve graduates, liquidity migrates to PumpSwap and the LP is burned.

03 / SECURITY

Signatures and security

Two signatures are required on the launch transaction: your wallet (fee payer / authority) and the freshly ground mint keypair. The mint keypair signs locally in your browser before the transaction is presented to your wallet. SpawnPad's server never receives any private key; it only re-verifies the confirmed transaction before listing a launch as verified.

04 / NETWORKS

Networks

Development defaults to devnet where the pump.fun program is officially deployed. Mainnet requires an explicit configuration change in settings/env — SpawnPad will never silently switch to mainnet.

Ready to try?Launch a token →