Developer reference
Contract architecture
Every component a fund launch deploys, how they bind, and who holds authority afterwards.
Loading…
Browse documentation
Developer reference
Every component a fund launch deploys, how they bind, and who holds authority afterwards.
Loading…
Developer reference
Every component a fund launch deploys, how they bind, and who holds authority afterwards.
Each Launchpad.launch atomically creates a fund graph and an official ERC-20 LP token. Launches share USDG settlement, deployment factories and the configured Uniswap V4 PoolManager/hook.
Launchpad
-> Coin -> Mine (permanent mint authority)
-> Fund (ownerless treasury)
-> SignalCoin -> Resonance
-> Base Auction -> BribeRouter -> Bribe
-> Coin Auction -> BribeRouter -> Bribe
-> LP Auction -> BribeRouter -> Bribe
-> Asset Auctions (app/SDK allow 4 extras at launch) -> BribeRouter -> Bribe
-> ResonanceRouter -> Resonance
-> FundController -> Coin + Mine + Resonance + official LP token configuration
-> FullRange hook -> FullRangeERC20 (official LP token)
-> PoolManager market (shared by LP tokens with the same pair, fee, spacing and hook) + this token's hook-owned position
-> 0x000000000000000000000000000000000000dEaD (initial launch shares)The Coin address is the launch identity. CoinDeployer uses CREATE2 with the launchpad, creator and creator nonce. The canonical launch event and getLaunch record the completed component graph.
The creator provides the reviewed base seed, while the launch mints the reviewed Coin seed and optional creator allocation. Seed amounts determine price. Initial official LP shares are locked, then Coin minting is permanently assigned to Mine. The creator grant may be automatically allocated to the LP auction or be split across the launch’s auctions. All creation steps revert together on failure.
The hook separates principal from fee credits. Each LP token has its own supply, configuration owner and pair of creator fee destinations, and several LP tokens can share one market. Every first deposit locks 1,000 raw shares; public pool creators receive the remaining seed shares. The FundController can configure compatible LP tokens that it owns; it cannot withdraw another holder's principal.
Protocol fee policy belongs to the FullRange owner. When enabled, collected swap fees split 70% creator and 30% protocol; when disabled, creators receive 100%. Claims pay the destinations set when they are made, including fees credited earlier. Mining fee configuration remains separate.