Solana token launch checklist

Start with what you cannot undo

The useful way to order a launch is not by urgency but by reversibility. Some decisions are permanent artefacts that every future evaluator will read; others can be fixed next week at no cost. Teams consistently spend launch day on the second category.

Permanent: the chart shape produced in the first days, the holder distribution created at launch, the transactions in the first blocks, and anything you did with contract permissions before someone checked. None of these can be edited later, and all of them will be read by exchanges, partners and traders for as long as the token exists.

Reversible: the website copy, the social presence, the pool depth, the metadata, and every piece of activity from tomorrow onward. All of these respond to work done at any time.

Spend your scarce launch-week attention on the first list. The second list will still be there.

Contract permissions, which take five minutes

Two fields on the mint account decide how the token reads to anyone performing diligence, and both are checked in seconds by people who do this often.

• Mint authority. Disable it unless you have a concrete reason not to. Live mint authority means supply can be created at any time, and it ends most evaluations on the spot.
• Freeze authority. Disable it. For an ordinary community token there is essentially no legitimate need, and its presence is the mechanism behind most of the situations described in the sell failure guide.
• Update authority on metadata. Decide deliberately whether to retain it. Retaining it is defensible; not knowing whether you retained it is not.
• Token extensions. If you used any, be able to explain exactly what they do, because buyers will ask and the honest answer is checkable.

If you keep any of these enabled, say so publicly and give the reason before anyone asks. Disclosure costs nothing and removes the worst interpretation.

The pool, which decides everything downstream

Depth is the single highest-leverage pre-launch decision and the one most frequently set by whatever budget happened to be left over.

The test is concrete rather than a target figure. Simulate an ordinary buy of the size a real trader might send and read the price impact. Then simulate the sell, because pools seeded mostly on one side absorb the two directions very differently. If either leg moves the price more than a percent or two, the token will produce a jagged chart, punish everyone who participates, and waste any budget spent on visibility.

Lock the position or burn the LP tokens, and publish the transaction rather than only announcing the fact. The difference between an announcement and evidence is the difference between a claim and a check, and buyers perform the check. The locking guide covers what this proves and, more usefully, what it does not.

Metadata and having something to arrive to

This section costs nothing and is skipped more often than any other, because on launch day it feels like the least pressing item on a long list.

Name, symbol, description, and an image hosted somewhere permanent that actually loads. A social presence with more than three posts. A pinned message containing the mint address, because the token will not be searchable by name for a while and everyone arriving in week one will need it.

The specific damage of skipping this is that it converts neutral visitors into negative ones. Someone who never saw the token remains a possible future buyer. Someone who saw it, clicked through and found an empty shell has made a decision, and people do not revisit decisions like that.

Launch day itself

Launch day is mostly execution, and the main risk is doing something on it that becomes permanent.

1. Seed liquidity before announcing. An announcement that arrives before a tradeable pool sends motivated people to a dead end.
2. Do not buy your own launch across many wallets. That is bundling, its trace is structural and permanent in the holder list, and it is the most examined pattern in any post-mortem.
3. Watch the first transactions. If sells are failing while buys succeed, you have an asymmetric pool and you need to know within minutes rather than after the complaints.
4. Publish the diligence evidence. Authorities disabled, liquidity locked, transactions linked.
5. Do not spend the whole budget today. Today is the day with free attention.

Week one, which is where launches are actually lost

Launch-day attention is structural: new-pair feeds surface anything new, launchpad boards show whatever is filling, and anticipation peaks by definition at the moment of launch. All of it expires within hours and nothing replaces it automatically.

The result is a cliff that teams read as rejection and that is closer to a subscription lapsing. Discovery surfaces read recent activity, so a token with nothing happening drops off them entirely, and it drops from a baseline that was never earned.

What works in that week is unglamorous. Something to say on most days, even if it is small. Activity attached to those moments rather than to a random Tuesday. And patience with the shape, because several moderate periods of activity read as a token people return to, while one large burst reads as exactly what it was. The week-one failure guide covers the sequence in which this usually goes wrong.

One planning habit separates launches that survive week one from those that do not, and it is simply writing down what happens on each of the first fourteen days before day one arrives. Not a marketing plan, a list: what gets posted, what gets shipped, when activity runs and against which event. The exercise takes an hour and its main value is revealing how empty days three through nine currently are. Almost every team discovers at that point that their entire plan was launch day, which is exactly the problem, and an hour spent finding that out beforehand is considerably cheaper than discovering it live.

The whole thing in order

Disable mint and freeze authority. Write complete metadata with a working image. Prepare socials with real content. Seed the pool and test both directions. Lock or burn, and publish the evidence. Announce only once the pool is live. Watch the first hour of transactions for asymmetry. Then plan days two through fourteen, and budget for the quiet week rather than the loud day.

Nothing on that list is difficult. The reason it goes wrong is that the permanent items are cheap and boring while the reversible ones feel urgent, and launch week rewards whichever gets attention first.