Token Launch Checklist: Everything You Need Before Listing

Decide which entity issues the token and where it sits, and get that decided before anything is public. The choice drives tax treatment, banking access, exchange onboarding, and whether counterparties can contract with you at all. Common structures pair an operating company with a separate issuing foundation or company in a jurisdiction with a recognised digital asset framework.

Close the supporting items: legal opinion on token classification in your target markets, terms of sale, privacy policy, sanctions and KYC procedures for any direct distribution, and a documented position on which markets are excluded. Exchanges ask for several of these during listing review.

Publish a supply table that reconciles: total supply, circulating at TGE, allocation by bucket, cliff and vesting per bucket, and the address holding each tranche. Inconsistencies between your deck, your docs, and on-chain reality are found within hours and are treated as dishonesty rather than error.

Model the unlock schedule against your liquidity plan. A cliff landing during a thin market is the single most predictable cause of a chart that never recovers, and it is entirely avoidable at the design stage.

Engage a provider six to eight weeks out, run a competitive process on one written specification, and sign a mandate with a real KPI schedule. Size the DEX pool deliberately and set concentrated ranges with intent. Fund working capital — both token and stablecoin — well before launch week so transfers are not happening under time pressure.

Complete exchange sub-accounts, API keys, and a dry run. On listing day the desk quotes at the open.

Pick two venues for day one rather than six. Prepare the application pack: corporate documents, token documentation, audit reports, tokenomics, liquidity commitment schedule, and named contacts. Understand each venue's listing fee, market making expectations, and any marketing commitments attached.

Sequence additional listings as milestones tied to demonstrated volume. Applying everywhere simultaneously and being rejected leaves a paper trail that other venues notice.

Decide where treasury tokens live: qualified custody, multisig, or a combination, with a documented signer policy and recovery plan. Establish stablecoin operational accounts and, critically, fiat banking for the operating entity before launch — payroll, vendors, and exchange settlements all need it, and digital asset banking takes weeks, not days.

Xavion Capital's core practice is exactly this: cross-border entity structuring and banking access for digital asset businesses. It is also the workstream founders start last.

Smart contract audit completed by a recognised firm, with findings remediated and the final report public. Ownership and admin key policy documented, ideally with timelock. Bug bounty live before launch. Multisig thresholds tested with a rehearsal transaction, not on the day.

Also verify the boring things: contract verified on explorers, correct decimals, accurate token metadata and logo submissions to aggregators, and the contract address published in a place holders can verify against impersonation.

Prepare the announcement sequence, the contract address verification post, aggregator listing submissions, and a moderation plan for the inevitable impersonation attempts. Assign a named incident owner for the first three days and agree in advance what constitutes an incident worth a public statement.

Set expectations internally too. Early price action is noise. Your measurable objectives for day one are book quality, absence of operational failures, and clean verifiable information — not the candle.

Every workstream above needs a single named owner, not a committee, and a date it must close by relative to TGE. In practice: legal wrapper and jurisdiction closes at T-minus ten to twelve weeks, owned by founders with external counsel; tokenomics and audit findings close at T-minus six weeks, owned by the technical lead; liquidity mandate signed and funded at T-minus two weeks, owned by whoever manages treasury; exchange applications submitted at T-minus eight weeks, owned by whoever holds the exchange relationships.

Run a single tracking document that shows all seven workstreams against these dates, reviewed weekly from T-minus twelve. The projects that slip are almost never the ones with a bad plan — they are the ones where nobody was checking the plan against the calendar until it was too late to recover a slipped dependency such as banking or an audit.

In the week before TGE, rehearse the actual sequence of transactions: the token generation transaction itself, the liquidity deposit into the pool, the transfer of trading capital to exchange sub-accounts, and the multisig approvals each of these requires. Do this on a testnet or with small real amounts if the mainnet contracts are already live, and time it.

This surfaces the problems that are expensive to discover live: a multisig signer travelling with no connectivity, an exchange sub-account that has not actually been funded despite confirmation emails, a pool deposit transaction that reverts because of a decimal mismatch. None of these are dramatic individually, but any one of them on launch morning turns a planned listing into a visibly chaotic one.

The first seventy-two hours get the attention, but the first week is where early problems either get fixed quietly or calcify into a pattern holders notice. Review depth and spread daily against the KPI schedule, not just on listing day, and hold a short check-in with the market maker at the end of week one specifically to discuss what real trading flow has revealed about pool sizing and range placement.

This is also when the first genuine arbitrage flows appear between the DEX pool and any centralised listing, and when the first wash-trading or spoofing attempts by opportunistic external actors — as distinct from your own provider — tend to surface on smaller venues. Have someone watching for both, because week one sets the reference price the market will anchor to for months afterward.

Founders frequently underestimate what liquidity actually costs across a launch cycle: working capital tied up in the pool and exchange accounts, provider fees or option premium, and the opportunity cost of tokens that cannot be sold elsewhere while committed to market making. Build a twelve-month liquidity budget alongside the rest of the treasury plan rather than treating it as a line item decided in the final weeks before TGE.

Revisit the budget at each listing milestone. Adding a second exchange without adding proportionate working capital simply thins both books, and it is a far more common cause of a disappointing second listing than anything the new exchange did wrong.

Exchange applications, legal opinions, and investor diligence all draw on the same underlying document set, so assemble it once as a shared pack rather than recreating it for each request. That pack should include the entity structure chart, token classification opinion, terms of sale, audit report, tokenomics and vesting schedule with wallet addresses, the market making mandate summary, and a one-page factsheet a listing team can circulate internally without needing a call to fill gaps.

Assign a single owner to keep the pack current as facts change — a vesting amendment or a new audit finding that is not reflected in the version sent to an exchange creates exactly the kind of inconsistency reviewers flag as a red flag rather than an oversight. Version and date every document, and keep a simple index so nobody has to ask which file is current.

Week eight: finalise entity structure and legal opinion if not already closed, and issue the market maker specification to shortlisted providers, owned by founders and counsel. Week seven: begin exchange application conversations and confirm audit scope, owned by the founder handling exchange relationships. Week six: audit findings remediated and final report published, tokenomics table locked, owned by the technical lead.

Week five: sign the market making mandate and open exchange sub-accounts, owned by treasury. Week four: fund working capital in token and stablecoin, complete banking setup, owned by treasury and finance. Week three: dress rehearsal of the full transaction sequence, owned by the technical lead with treasury present. Weeks two and one: final aggregator submissions, communications sequence drafted, and a named incident owner confirmed for launch week itself.

Reduce day-one monitoring to a small number of things that matter rather than refreshing the price chart. Watch spread against the committed band at set intervals through the day, confirm depth is present on both sides rather than only the side that looks better, and check that the DEX pool and any centralised book are tracking each other within a sensible tolerance. Confirm every planned transaction actually settled — pool deposits, sub-account funding, and any vesting contract deployment.

Have the named incident owner check aggregator listings for accuracy, since a wrong contract address or decimal figure propagating across a price site is a common and entirely avoidable first-day problem. Keep a simple running log of anything unusual, timestamped, so that if a genuine incident does occur there is already a record of what was normal beforehand to compare it against.