Going Live

Two transactions separate a configuration from a live market: the deploy (permissionless, one factory call) and the launch (team-only, one call, later). Everything between them is the raise. Nothing about either transaction is discretionary — both are all-or-nothing, and both are verifiable on-chain as they happen.

The deploy: one factory transaction

Deployment happens through the launch factory: one deployLaunch() call, carrying your inputs and the launcher-paid deploy fee, that deploys your entire six-contract set, wires it, verifies every wiring edge on-chain, and registers your launch in the public provenance registry. If anything is wrong, the whole transaction reverts — fee included — and a misconfigured launch simply cannot come into existence.

Two properties worth using:

• Your addresses are pre-computable. The factory derives your launch's addresses from your own address and a salt you choose, so you can know your token, treasury, and pair addresses before deploying — useful for listing preparation and pre-funding.
• Provenance is automatic. From the moment of deployment, anyone can verify your launch is genuine PURITY via the factory registry — a check that works even if every website is down. Point your community at it.

The deploy fee (readable live from the factory, initially 0.1 ETH) is a launcher service charge — it is not launch capital and touches neither your buyers nor your market.

The launch: one team-only transaction

When your raise has reached at least the committed minimum — and ideally when it has filled to the level you want, since surplus becomes your engine's capital — you fire launch() from your team address. You control exactly one thing here: timing. The amounts are immutable commitments, the sequence is fixed, and any caller other than your team address reverts.

One atomic transaction does all of it: pulls the vault's raise into the Treasury, seeds the canonical pool with 100% of your token supply, executes the committed initial accumulation (establishing the Treasury's opening supply position), lifts the transfer whitelist irreversibly, and opens trading. There is no intermediate state — an under-funded launch reverts entirely (leaving the vault refundable), and a successful one leaves you with a live market and a running engine in the same block.

The mechanics of what happens inside that transaction — and the finite launch-phase sell program that follows it — are specified in Launch & Initialization and Liquidation Logic.

From this block onward, your launch is in autonomous operation — and your role changes from launching to operating.