Launching a token
What happens when you press launch, and why a refresh can never create two tokens.
The transaction
UnicornSI builds pump.fun's official create_v2 instruction with the official @pump-fun/pump-sdk, paired with SOL. The token name can be up to 32 characters, the ticker up to 13 and the metadata URI up to 200, exactly as pump.fun's program enforces.
Before you sign, the transaction is simulated against Solana mainnet. If the simulation fails, the approve button stays disabled.
Who signs
A fresh mint keypair is generated in your browser and signs only the creation of the mint. Your wallet signs as creator and payer. The server checks the signed transaction is the one it prepared, records its signature, and only then broadcasts it.
Confirmation
Your project goes live only after the chain confirms the transaction succeeded, touched the pump.fun program and created a bonding curve with your wallet as creator. If you refresh, close the tab or lose connection, the launch resumes by checking that same transaction; it is never re-sent as a new token.
Metadata
The token metadata (name, ticker, description, image, links) is stored content-addressed: its URL contains the SHA-256 of the JSON, so it cannot change after launch. When IPFS pinning is configured, metadata and images are pinned to IPFS instead.
