Pre-Launch

The pre-launch phase begins when the launch's contract set is deployed and ends the instant launch() executes. It is a genuine on-chain state with precise properties, not a waiting room.

What exists during pre-launch: the entire contract set, fully deployed and immutably wired — token (its full supply already minted, sitting in the Treasury), Treasury, both distribution contracts, vault, and governance. Even the canonical pair already exists, created empty by the Treasury's constructor.

What does not exist: a market. The pool is unseeded, the token's launch whitelist confines every token to the Treasury and pair, no trading is possible, and the engine's entrypoints all revert. Nothing about the launch's economics can happen yet — which is exactly what makes the phase safe.

The action is in the Supporter Vault. Contributions accumulate toward the launch's committed minimum, under the per-wallet and overall caps, gated by the whitelist if the admin enabled one. Two properties define the phase's honesty:

• Every contributor can leave at any moment. Refunds are unilateral and unblockable until the instant of launch.
• Nothing can be taken early. The vault will release its balance only to the Treasury, only inside launch(), and only if the raise reached its minimum. The team has no access to a single wei of it during the raise.

The phase ends in one of two ways. Either the raise fills and the team fires launch() — the atomic transition described next — or it never fills, no launch ever happens, and every contribution remains refundable indefinitely. There is no third outcome, and no deadline forcing a bad one.