Docs
Start building
How-to Guides

Launch a token the safe way

Testnet rehearsal → audit → mainnet → locked liquidity, in the right order.

2 min read · 5 sections

On-chain mistakes don't get patched, so the order of operations is the safety. This is the sequence for an EVM token launch that holders can trust. (On Solana the steps differ; see Launching on Solana.)

Rehearse on testnet
Read the audit
Deploy mainnet
Add liquidity
Lock the LP
Enable trading

Rehearse on a testnet

Run the interview, approve the spec, and deploy to Sepolia or Base Sepolia first. It's free, and it's a full dress rehearsal: same contract, same wallet flow, same deploy report. Poke at the owner functions there, not on mainnet.

Read the audit like you mean it

Before deploy unlocks, the contract passes a three-layer audit, and every critical or high finding must be fixed; that gate can't be talked around. But read the mediums too: they're judgment calls Modus made visible so you can make them. Click any guidance chip (high tax, snipe risk) and have the launcher walk you through it.

Deploy with trading off

For a fair launch, ship with trading disabled. A token that's tradable the moment it exists, before liquidity is in place, is an invitation to snipers, and it's exactly the pattern the guidance chips warn about.

Liquidity, then lock, then open

In the same chat: add the liquidity pool (Uniswap, PancakeSwap, or Aerodrome depending on chain), then lock the LP with UNCX or Team Finance, or burn it. Only then enable trading. The lock is the point: it's the on-chain proof you can't pull the pool out from under your buyers, and it's the first thing a careful holder checks.

Decide what you keep

You still hold owner powers: tax changes, blacklist, the trading switch. Keep them while you need them, and when the token should stand on its own, renounce ownership from the same conversation. Every one of these is a wallet signature of yours; Modus never holds the token, the pool, or the keys.