Skip to main content
The create form mints a fresh LaunchToken for you. The entire supply is minted once, at deployment — there is no mint function and no minter role granted to anyone. The cap you set is the cap that will ever exist.

What you set

FieldMeaningNotes
nameToken namerequired
symbolTickerrequired
decimalsToken decimalsdefault 18, range 0–36
totalSupplyFixed total supplymust be ≥ sale + LP requirement

How the supply splits

Your totalSupply is divided three ways at launch:

Sale

The tokens buyers can purchase, deposited into the sale contract.

Liquidity

The token side of the locked LP (lpTokensAmount), deposited alongside.

Team / treasury

The remaindertotalSupply − sale − LP. Whatever’s left after the sale and LP allocations.
Unsold sale tokens are burned, not returned. So size totalSupply to what you actually want circulating — over-allocating to the sale just burns the excess at settlement.

The team remainder

In the app today, the team remainder is sent to your wallet instantly at launch. The contracts do support vesting it (cliff + linear via a dedicated TokenVesting wallet), but the create form hardcodes team vesting to off. See Vesting for how to use it via a direct contract call.

Token0 ordering (automatic)

To make the V3 pool cheaper and more predictable, the form mines a CREATE2 salt so your token’s address always sorts below the quote token — making it token0 and removing a pool ordering branch. This is fully automatic; you don’t configure it. The salt is namespaced to your wallet so no one can front-run your launch to the same address.