Launch flow
What the transaction does, step by step.
A launch is one call to the factory. It either completes every step below or reverts entirely — there is no partially created market, and nothing is registered until the market fully exists.
Inside the transaction
- Validate. The name, ticker, supply, model, schedule, opening tick and allocation are checked against the registry's bounds. The hook re-checks the schedule when the pool is initialised, so a market that reached the pool was validated twice by two contracts.
- Deploy the token. A fixed-supply ERC-20 at an address derived from your own address and a salt, so a memorable address is available to you without letting one creator occupy another's.
- Open the pool. At the opening tick you chose, with tick spacing 200 and a dynamic fee flag that hands fee decisions to the hook.
- Provide the liquidity. The supply, less any allocation you withheld, goes into a single one-sided position. There is no ether in the pool at this point; the first buyer brings the first of it.
- Lock the position. The position NFT is transferred to a locker holding it for the market's life.
- Register. Last, so the public record only ever describes a market that exists in full.
What you decide
| Choice | Range | Changeable later |
|---|---|---|
| Name and ticker | 32 and 11 bytes | No |
| Supply | 1,000,000 to 1,000,000,000,000,000 tokens | No |
| Fee | 0.01% to 10% | No |
| Schedule | 1 to 8 stages, up to 730 days out | No |
| Your allocation | 0% to 20% of supply | No |
| Vesting | 30 to 730 days, or none | No |
| Fee recipient | Any address | No |
| Metadata | A document the token points at | Only if you choose mutable |
Your first buy is a second transaction
The factory does not accept ether, so the launch cannot include a purchase. Buying is an ordinary swap you sign afterwards, and in the gap between the two anyone else can trade. Bundling the first buy into the launch is planned work; until it lands, treat that gap as real.