Launch a token
Create a fixed-supply ERC-20 and its Uniswap V3 market.
A Spawn launch deploys a fixed-supply ERC-20, creates its Uniswap V3 market, provides the configured token liquidity, and executes the first buy in one factory transaction.
Before launching
Prepare the following values:
| Field | Contract use |
|---|---|
| Name | ERC-20 name and launch registry entry |
| Symbol | ERC-20 symbol and launch registry entry |
| Logo | On-chain URL returned by logo() |
| Description | On-chain text returned by description() |
| Social links | Five strings returned by socials() |
| Fee recipient | Wallet that receives 70% of collected LP fees |
| Referrer | First-touch referral wallet, or the zero address |
| Initial buy | ETH used for the mandatory first swap |
The factory reads a minimum from initialBuyAmount(). The amount shown in the launch form is checked again just before the transaction is sent.
Launch from the app
- Open Launch and connect the wallet that will be recorded as the deployer.
- Sign the login message so Spawn can apply any saved referral attribution.
- Enter the token identity and upload a logo.
- Add a useful description and any public social links.
- Confirm the LP fee recipient.
- Enter an initial buy at or above the displayed minimum.
- Review the wallet value and factory address, then sign.
The transaction emits ERC20TokenCreated. Spawn extracts the new address from that event and waits for the indexer to add the market.
What the factory creates
Each token has 1,000,000,000 × 10^18 base units. The full configured token allocation is supplied to the initial pool position. The token contract stores its deployer, launch factory, position manager, DEX factory, paired token, description, logo, and socials.
The public app uses parameter set 0, split value 0, and a random 32-byte salt. The factory can adjust its permitted launch parameters and can pause new token creation.
After confirmation
Open the token page from the feed and verify the contract address. The page shows indexed trades and market data while balances, pool identity, and metadata remain readable from the token and factory contracts.
Use Token metadata to read the new contract directly. Use Launchpad write calls to launch from an integration.
Common launch failures
DeployDisabled means the factory owner has paused launches. InsufficientInitialBuy means the submitted ETH is below the current minimum. InvalidFeeRecipient means the fee wallet is the zero address. InvalidReferrer means the launch tried to use its own wallet as the referrer. A wallet can also reject for insufficient ETH or a network mismatch before the call reaches the factory.