Deployer guide
Publish one immutable launch configuration and understand what can never be changed afterward.
A deployer calls D17Factory.createLaunch once. The factory validates the full configuration, creates the launch token, launch contract, and liquidity vault, mints the declared supply destinations, closes minting, completes one-time wiring, and registers the launch as canonical.
There is no setup transaction after createLaunch. A successful launch is born complete; an invalid configuration reverts atomically.
What you choose
- token identity, description, compact SVG data URI, and up to eight HTTPS links;
- total supply and exact sale / LP / creator / dead-address split;
- treasury address and WETH percentage;
- start time, five individual round lengths, five sale shares, one refund-window length, and one settlement length;
- minimum commitment, round-1 WETH floor, and minimum anchor price;
- one global refund-penalty percentage; and
- whether unsold sale tokens burn.
What the contract fixes
- exactly five rounds;
- ordinary refund windows after rounds 1–4 only;
- rounds 1–2 penalty-free and rounds 3–4 charged at your single published percentage;
- manual distribution recipient = the
createLaunchcaller; - canonical dead recipient when a dead allocation is non-zero;
- one-time mint closure and token ownership renunciation;
- permissionless finalization, post-grace settlement, and pool creation; and
- permanently held protocol LP tokens.
No administrative correction path
Review every address, amount, timestamp, and unit before signing. Existing launch terms cannot be edited. If a factory suite itself is deployed or pinned incorrectly after ownership renunciation, recovery is a new factory deployment, not an administrator repair.