Launch

Launching under PURITY means deploying your token into a pre-built, non-extractive market structure — and accepting its constraints in exchange for what they buy you: a launch no one can accuse of hidden allocations, a treasury no one can drain, and a set of guarantees your buyers can verify on-chain rather than take on faith.

This section is the practical path, in order: what you decide up front (this page), the raise, going live, and operating post-launch. It describes launching at the contract level, which is locked and fully specified. A hosted platform that wraps this flow in a guided interface is in active development; where these pages mention it, treat the details as indicative — the platform layer is still being finalised, while everything at the contract level is final.

What you decide — and what you don't

A launching team makes a small number of genuine decisions:

• Token identity — name, symbol, total supply.
• The raise shape — the committed pool-seeding and accumulation amounts (which together set your vault's go-live minimum), the overall raise cap, and the per-wallet cap. Covered in The Raise.
• Your team address — the single address (use a multisig) that will hold the team's three powers: firing launch(), claiming vested compensation, and proposing treasury releases.
• A vault admin — who manages the optional contribution whitelist and can wind down an unfilled raise.
• Optionally, the engine configuration — every market-making parameter is adjustable within the protocol's enforced ranges. Most launches should simply take the defaults, which are the audited $PURE values; the ranges exist for teams that know precisely why they want something different. Whatever you choose is public, immutable, and validated at deployment — an out-of-range configuration cannot deploy. The ranges are tabulated in Reference.

Equally defining is what you cannot choose. You cannot allocate tokens to yourselves or anyone else — the entire supply enters the pool at launch. You cannot choose your arbitrator — PURITY's multisig is wired into every factory launch identically, which is precisely why your holders can trust that you hold no shutdown power over them. You cannot waive or reduce the 500 bps ecosystem contribution. And you cannot change any of it later: there are no parameter setters, for you or anyone.

The shape of the journey

Three moments, two of them on-chain:

1. Deploy — one factory transaction that creates your entire wired contract set and opens your raise. Nothing can trade yet.
2. The raise — supporters (or you yourself) fund the vault toward your committed minimum. Every contributor can refund at will until launch.
3. Go live — one team-only transaction: the raise is pulled, the pool is seeded with the full supply, initial accumulation runs, trading opens, and the autonomous engine takes over.

From then on the launch mostly runs itself, and your ongoing role is deliberately small — one operational duty and two recurring interactions, covered in Operating Post-Launch.