sqrtDAO docs

Launch a token

A full launch is one call to createTokenAndLiquidityAndDistribution on FactoryV1: it deploys your ERC20, opens its Uniswap V3 pool, and starts an epoch-based distribution — all in a single transaction. The wizard in the app walks these same fields; this page explains what each decision means.

1. Token

Name, symbol, and the initial allocation list (recipient + amount pairs) that is minted at construction. One thing to get right: the factory itself must be allocated total distribution amount + your liquidity deposit of the new token — it funds both the distributor and the pool from that allocation. The wizard handles this automatically.

2. Market

  • Starting price. Expressed as sqrtPriceX96, the Uniswap V3 price encoding. This sets where trading begins.
  • Liquidity. How much participation token and new token you seed the pool with. Leftover deposits are refunded to you after minting.
  • Locked forever. The fee tier is fixed at 0.3% and LP tokens are minted straight to the dead address — nobody can ever withdraw this liquidity, including you.

3. Distribution

The sale side of the launch — each field maps straight onto DistributorConfig:

  • Epochs. Count and duration. 100 epochs × 1 hour = a ~4 day slow sale; longer windows smooth out price discovery.
  • Emission curve. How much of the supply each epoch releases: fixed, linear ramp, or exponential decay (front-loaded). See epoch-based distribution.
  • Minimum participation. Filters dust entries per epoch.
  • Claim delay. A cooling-off window between an epoch ending and claims unlocking.
  • Allowlist (optional). Restrict early epochs to signed wallets; opens permissionlessly after the deadline.

4. Shares & hooks

When each epoch drains, its fund splits across configured shares. The protocol fee share is injected automatically, so the shares you configure must sum to 100% − protocol fee. The interesting choice is the buy back & burncut: a percentage of every epoch's fund permanently bought off the market and burned. See buy back & burn. Remaining shares can route to any address via TransferToHook (e.g. treasury, team vesting).

5. Sign & deploy

  1. Approve the tokens — or sign Permit2 permits, which the factory accepts for gasless-style approvals without pre-setting allowances.
  2. Submit the launch transaction.
  3. You receive two addresses: your token and its distributor. Verify both on the explorer and share the distribution link — participants do the rest.
After launch there is nothing to operate: epochs run on time alone, and anyone can permissionlessly trigger each epoch's drain. Your only job is talking to participants.