The Monad Token Launch Checklist

A diligence checklist, not a growth checklist. Every item exists because someone will later ask you to evidence it — and on this chain, the person asking knows what they are looking at.

What does a token launch checklist look like on Monad?

It looks like preparation for examination rather than a growth plan, because Monad’s capital is institutional and the counterparties who decide whether your token is worth their time read cap tables for a living. Total value locked on the chain is $957.23M as of September 2026, sitting in Aave V3 at $320.94M, K3 Capital at $310.9M, Euler V2 at $241.67M, Pendle at $221.76M and Morpho Blue at $172.96M — lending, yield and structured-credit venues. Mainnet has been live since November 24, 2025. That is the audience your launch lands in front of, and it is not an audience that rewards momentum theatre.

It runs in five phases: pre-deployment decisions, deployment, liquidity — which forks sharply by launch route — team and treasury allocations, then distribution and verification. Work them in order; the early decisions are effectively irreversible.

What has to be decided before you deploy anything?

Supply, allocation percentages and the release calendar — the three decisions that become extremely expensive to change once a contract exists and a market has formed around it. Everything after deployment is execution; this phase is where the cap table is actually written.

Write allocations as percentages of total supply — team, treasury, investors, community, liquidity — because percentages are the unit every reader converts to anyway. Set the release calendar at the same time, since a schedule invented after launch reads as a reaction and one published before it reads as a commitment. Decide who signs and whether contract ownership will be renounced.

MON itself is a useful reference, as market structure rather than criticism: it circulates 11.83B of 100.68B total supply against a $2.6B fully diluted valuation as of September 2026, roughly a 12% float. Most of the eventual supply is still ahead of the market, and how it arrives is a schedule question.

What happens at deployment, and what does it not settle?

Deployment produces a contract and a supply and settles nothing about who holds what — which is why it is the shortest phase here despite being the one people treat as the launch. Creating a token on Monad through MintPlus is free as of September 2026, so the constraint is not cost; it is that a deployed contract is evidence of nothing except deployment. Create a token on Monad covers the choices that cannot be undone.

Which liquidity route are you on, and why is that the fork in this checklist?

Your liquidity checklist has either no items on it or all of them, depending on whether a protocol placed the liquidity or you did — and this is the single most important question on the page. Nearly every launch checklist written for other chains assumes the launcher holds LP tokens and needs to lock them. On Monad that assumption is wrong for anyone who used the main bonding-curve venue, and acting on it wastes time chasing a transaction that cannot be signed.

Answer one question before anything else: did LP tokens ever land in a wallet you control? If a protocol handled liquidity at graduation, they did not. If you pooled yourself, they did. The two branches below are mutually exclusive.

If you launched on nad.fun, what is left on the liquidity line?

Nothing — nad.fun locks the protocol-provided liquidity itself at graduation and the creator never receives LP tokens, so the liquidity line is closed before you reach it. The protocol states the mechanism in its own documentation: “The initial protocol-provided liquidity is locked through its LP tokens, and the LP fees earned by this locked liquidity stay in the pool and help deepen liquidity over time.” Graduation occurs when “the bonding curve has gathered around 225,000 MON and approximately 80% of the token supply has been sold”, at which point “the remaining token supply and gathered funds are moved to an internal DEX liquidity pool”. Under legacy V1, creators received “50% of the remaining LP fees” — fees only, never the LP tokens themselves.

So cross the line off and do not let anyone re-add it. Advice to lock your nad.fun liquidity describes a transaction that does not exist. After nad.fun graduation: what’s already locked and what isn’t sets out where the work moves next — the team allocation, the treasury and advisor grants. For scale: nad.fun holds $411,668 of total value locked as of September 2026 and its revenue is down 84% from its Q4 2025 peak of $958.2K to $150.25K in Q3 2026. The capital above weighs your allocations far more heavily than your curve.

If you created your own pool, what is left on the liquidity line?

Everything — you hold the LP tokens, no protocol locked them on your behalf, and coverage, duration and expiry are all live decisions with real consequences. This is the branch where a liquidity lock is a genuine commitment rather than a misunderstanding, and where its absence is a legitimate question for anyone assessing you.

Decide what share of the position to lock, for how long, and what happens at expiry — an expiring lock returns a withdrawable position to you, so the end date is a scheduled decision rather than an ending. How to lock LP tokens on Monad covers the mechanics; how to lock liquidity on Monad covers what a lock proves. A liquidity lock is $150 as of September 2026, fixed in USD and charged in MON.

Know your venue, because it changes what exists to lock. Kuru carries roughly 71.7% of Monad DEX volume as of September 2026 and is a central-limit orderbook rather than an AMM, so market-making there mints no LP tokens in the AMM sense; the AMM venues behind it are Uniswap at 10.5% of volume, Metric at 5.6%, Hanji at 4.6% and Balancer at 3.2%. And if you raised through Alloca, an IDO platform rather than a bonding curve, its liquidity mechanics are not publicly documented — establish who holds the position first.

What has to happen to team and treasury allocations?

This is where most of the real work sits on Monad, whichever liquidity branch you came down, because the allocations that were never in a pool are the ones a counterparty examines first. A liquidity lock addresses the pool; it says nothing about the founder tranche, the treasury or advisor grants.

Choose the instrument per allocation: a single-cliff lock for anything that should be immovable until one date, a vesting schedule for anything that should arrive gradually. Team token locks on Monad covers what a team lock proves that a liquidity lock cannot, how to set up token vesting on Monad covers construction, and vesting schedules for Monad projects covers cliff sizing. A team or token lock is $150 and vesting is $100 as of September 2026, each charged in MON, per lock rather than per token.

Then publish the calendar: an unlock nobody was told about is indistinguishable from an unlock nobody intended to disclose.

What about distribution and anything that recurs?

Distribution is a one-way operation and recurring payment is a commitment, so both belong on the checklist before the first send. Paying contributors from an allocation you have publicly committed to a lock is a contradiction that surfaces at the worst possible moment.

Send tokens to many addresses on Monad covers list validation, the errors that cost real money, and how recurring pay is reconciled against lock and vesting commitments. Multisender is $50, an airdrop is $100 and payroll is $100 as of September 2026, each fixed in USD and charged in MON.

What will a counterparty check after you launch?

They will check coverage, duration, token identity, expiry and the date of your next cliff — five details that survive a careless glance and fail a deliberate one. Every one of them is readable on MonadVision, the chain’s block explorer, without your cooperation, which is the entire point.

Run the check on yourself first. How to verify a lock on Monad sets out the reviewer’s procedure: establish the token contract independently — from a market data application such as <a href="https://thecrypto.app" target="_blank" rel="noopener noreferrer">The Crypto App</a> — read the holder distribution, then read the terms from the holding contract. If you launched through nad.fun, expect no third-party lock record for liquidity and be ready to explain why its absence is correct.

What does the checklist cost end to end on Monad?

Creating the token is free and staking pools are free; the priced items are a liquidity lock at $150, a team or token lock at $150, an NFT lock at $150, vesting at $100, a multisender run at $50, an airdrop at $100 and payroll at $100 — all as of September 2026, fixed in USD and charged in MON. Nothing is taken as a percentage of the tokens involved, which is the comparison that matters at treasury scale. Services run from app.team.finance and www.team.finance; larger launches, TrustSwap contact.

What is the checklist, in order?

Seven phases, in sequence, because each constrains the next.

1. Fix supply, allocations and the release calendar. Write allocations as percentages of total supply, set cliff dates and release terms, and decide who signs — the choices that cannot be cheaply revised later.
2. Deploy the token contract. Configure name, symbol, decimals, supply and permissions and deploy, remembering that a deployed contract is evidence of nothing except deployment.
3. Identify which liquidity route you are on. Establish whether LP tokens ever landed in a wallet you control, because a protocol-launched token and a self-pooled token have different liquidity checklists.
4. Close the liquidity line for your route. If a protocol locked the liquidity at graduation there is nothing to sign; if you hold LP tokens yourself, decide coverage, duration and expiry, then lock.
5. Lock or vest team, treasury and advisor allocations. Choose a single-cliff lock for anything immovable until one date and a vesting schedule for anything that should arrive gradually, then publish the calendar.
6. Set up distribution and any recurring payments. Validate recipient lists before sending, and confirm the tokens earmarked for airdrops or payroll are not encumbered by a schedule you have committed to.
7. Verify everything a counterparty will check. Read your own coverage, duration, token identity, expiry and next cliff date on MonadVision, and reconcile them against every public claim you have made.

Done in this order, the diligence conversation becomes a reading exercise rather than an interrogation.

FAQ

Do I need to lock liquidity if I launched on nad.fun? No. nad.fun locks the protocol-provided liquidity through its LP tokens at graduation, so the creator never receives LP tokens and there is no position to lock. The work that remains is your team allocation, treasury and advisor grants.

What is the first thing on a Monad launch checklist? Supply, allocation percentages and the release calendar — the three decisions that become extremely expensive to change once a contract exists and a market has formed around it. Everything after deployment is execution; this phase is where the cap table is actually written.

What does a Monad launch cost end to end? Creating the token is free and staking pools are free; the priced items are a liquidity lock at $150, a team or token lock at $150, an NFT lock at $150, vesting at $100, a multisender run at $50, an airdrop at $100 and payroll at $100 — all as of September 2026, fixed in USD and charged in MON.

Next: create a token · lock liquidity · lock LP tokens · team locks · vesting · schedules · verify a lock · distribution · after nad.fun graduation · hub