Launch a coin.
What the creator supplies, what the transaction creates, and what makes a launch valid.
In this guide
Prepare your launch
Give the coin an identity
Set its name, ticker, description, image and links. Prepare durable metadata and media before building the transaction.
Choose the supply and community share
Review the complete distribution: rewards, curve sales and graduation liquidity. The selected engine must accept all amounts and decimals.
Publish the campaign terms
Commit the team-entry rules, eligibility, scoring, deadlines, ties, reward schedule and failure outcomes. Participants must know these before joining.
Review costs and authorities
Show the network, fees, custody location, mint policy, metadata control and upgrade powers. Any optional creator buy is a separate, ordinary trade.
Approve and confirm
The wallet signs the displayed transaction. A confirmed chain read must establish the mint, complete reserve commitment and matching launch configuration.
Create the mint, then mint the supply
On Solana, the mint address identifies the token. Its account records supply, decimals and mint/freeze authorities. Token accounts hold balances for that mint. Creating the mint account and issuing tokens are separate operations in the launch flow.
The native RalliPad reference design creates a mint, initializes the required vaults, issues the full initial supply into the three destinations, and then removes further minting authority. No freeze authority is part of the baseline. Metadata authority and program upgrade authority are separate controls.
A launch must secure its entire allocation
Creation must not expose trading while the community reserve is only a promise. The full allocation, its custody or beneficiary, and the immutable launch terms must be validated before RalliPad registers the launch as active.
In the native path, minting into the vaults, authority revocation and activation succeed together. In the LaunchLab reference path, engine initialization, full beneficiary assignment and RalliPad validation must compose atomically. If account preparation is staged, activation stays gated until the invariant is satisfied.
Solana executes the instructions within one transaction atomically: a failing instruction reverses the transaction’s state changes. Network fees can still be charged. This property does not make separate transactions atomic.
What a confirmed launch must expose
- The actual mint address and network, with a transaction/explorer reference.
- Initial supply, decimals and all allocation amounts.
- The curve engine, program/configuration identity and supported trading window.
- The reserve’s real custody account or external entitlement and fixed beneficiary.
- Campaign terms, applicable authority controls and disclosed costs.
A wallet connection, saved form, animation or transaction signature alone does not establish that minting and reserve commitment succeeded. The interface must reconcile the actual account state.