Your token's first 48 hours

The first hours: confirm what the chain recorded

Before anything else, verify that every transaction did what you intended. Deployment, pool funding and any lock each emit their own on-chain event, and a launch that half-completed is much easier to fix in the first hour than after buyers arrive.

Then read your own token page the way a stranger would. It exists already — Locksley builds it at pool creation, as described in your token page is born with your token — and your launch is already listed in new tokens and filterable in Explore. Check that supply, lock state and holder distribution render the way you expect. If they do not match your announcement, the announcement is what needs correcting.

If your pool is locked through a locker Locksley has not indexed yet, your page may show no lock at all. "No lock found" means we found none — not that none exists. Locksley does not yet index every locker. Tell us and we will read it; do not tell buyers the page is wrong without saying which contract holds the position.

Day one: what to watch, and what to ignore

Three things are worth watching on day one, mostly from a phone — The Crypto App, a sister product built by TrustSwap, lists price alerts and portfolio tracking among its own features.

Pool depth relative to volume. Depth decides how much a given trade moves your price. If volume is arriving in sizes that swing the chart hard, the honest explanation is thin liquidity, not manipulation — price impact is the mechanism, and it is arithmetic.

Holder spread. Watch how many wallets hold and how concentrated the top of the list is. Early concentration is normal and visible to everyone; holder concentration: what actually matters explains the difference between a signal and a scare.

Your own wallets. Every transfer from the deployer or treasury is public and reads as intent. If you must move tokens in the first days, say what the movement is for before you sign it.

Day two: the questions worth answering

By the second day the pattern of questions is clear, and answering them well is most of the early distribution work. Point people at verifiable state — the lock's release timestamp, the mint function's status, the pool's depth — not at roadmap promises.

This is also when to do the organic listing work properly. Screeners, aggregators and anything that names your project pull from the same on-chain data, and getting your token listed and noticed sets out the order to work through, organic first.

The unlock dynamic starts on day one

The moment you lock, you also create a date. Buyers track it, alert services publish it, and this week's unlocks lists positions approaching release across the chain, currently —pending of them in the next seven days.

That is a reason to choose a duration you can live with, and to communicate before the date rather than on it. What happens when a lock expires covers the mechanics from the holder's side, including why an expiry is not a rug but does change what is possible. A lock can generally be extended to a later date — lock liquidity through Team Finance, our sister product, costs $150 per use as of August 2026, plus gas in ETH — and lock liquidity, step by step walks the transaction. An unlock cliff on a vesting schedule works the same way: the date is public well before it arrives.

When to add vesting, staking or an airdrop

None of these belong in the first 48 hours. They are commitments, and commitments made in a panic about a quiet chart are the ones projects regret.

Once trading has settled, three tools do different jobs. Vesting locks team or treasury allocations on a published schedule — vesting your team's tokens covers schedule design, and Team Finance vesting costs $100 per use as of August 2026. A staking pool gives holders a reason to hold, funded by rewards you supply — create a staking pool is free for a limited time. An airdrop distributes supply to a list you define, at $100 per use, plus gas in ETH on all of them. Team Finance is our sister product, and it is a multi-chain Web3 token-management suite that projects and individuals use to lock liquidity, vest tokens, mint and manage supply across chains. We charge for the doing, never for the reporting. Paying never changes how a token's data displays.

What not to do in week one

Do not withdraw or reduce liquidity. Do not shorten a stated lock. Do not promise a price, a listing or a partnership you have not signed. Do not delete questions you find inconvenient — the addresses stay public whether or not the thread does. And if you change the plan you set out at the Robinhood Chain launch checklist stage, say plainly what changed and why.

Frequently asked questions

“No lock found” means we found none, not that none exists: we do not index other lockers yet, and it is never a claim about the project.