Token launch checklist
The sequence that has to be finished before a mainnet deployment: ownership model, supply decisions, liquidity plan, distribution list hygiene, and the controls that need to exist on day one rather than week three.
Resources
Guides, documentation, research, and product updates will publish here. This page is not padded with generated posts to look active — instead, below is the content architecture, the specific pieces in progress, and how far along each one is. If you need something on this list now, ask and we will prioritise it.
Streams
Operational walkthroughs for a specific job: preparing a distribution list, structuring a cliff, arming a strategy safely.
Project operators
Module reference — configuration options, validation rules, state transitions, and the service interfaces behind them.
Engineers
Longer analysis on market structure, distribution outcomes, and unlock mechanics. Published with method and data source stated.
Technical and strategic
What shipped in each module, what changed in behaviour, and what was deprecated. Dated entries, no roadmap theatre.
All users
In progress
The sequence that has to be finished before a mainnet deployment: ownership model, supply decisions, liquidity plan, distribution list hygiene, and the controls that need to exist on day one rather than week three.
Cliffs, linear release, unlock frequency, and revocation — what each parameter does to a holder's incentives, and the schedule mistakes that create a sell wall the quarter after launch.
Choosing between airdrop, claim, and direct allocation. Batch sizing and gas economics, eligibility criteria that survive scrutiny, and how to handle the failure and retry path without double-paying.
Where utility actually changes holder behaviour versus where it is decorative. Staking, gamification, and access mechanics assessed on retention rather than announcement value.
How spread, depth, and order frequency interact on thin books. What a market-making configuration can and cannot achieve, and the guardrails that keep a strategy from becoming the dominant participant.
Moving a live token between chains: snapshot and eligibility, bridge versus redeploy, holder communication, wallet risk controls, and the accounting reconciliation nobody scopes for.
The operational half of security: key custody, exchange API permissions, multisig thresholds, rotation when someone leaves, and dual control on treasury movement.
Holder concentration, transfer patterns, liquidity depth, and unlock proximity — which indicators predict trouble, and which are vanity metrics that look good in an update post.
Documentation
The Console sandbox is the most complete documentation that currently exists. Every module runs on fabricated data with its validation rules, states, and controls active — you can read the behaviour by using it.
Requests
If a specific guide would unblock a decision you are making, tell us which one. We will send what exists in draft and prioritise finishing it.