Token generation event: the sequence from lock-up to listing

Who decides this

The CEO and the head of markets own the TGE sequence. The CEO is accountable for the date, the public commitments and the decision to stop the clock if a gate is missed. The head of markets is accountable for liquidity, market-maker and exchange relationships, and for proving on the day that the order book the plan assumed actually exists. Counsel owns the filings, and the council or board approves the allocation. Neither should own the calendar.

What has to be locked before anything trades?

Every non-circulating allocation should sit in a deployed, verifiable lock or vesting contract before the first trade, not after it. Holders, analysts and exchanges will read the contracts on day one. A schedule that exists only in a token paper invites the assumption that it can be changed.

The stakes are well documented. Keyrock’s study of more than 16,000 unlock events, as reported by BeInCrypto, found about 90% put negative pressure on price. Team unlocks were the worst category, with average drops of up to 25%. A market that cannot see the team’s schedule will price in the worst case.

The practical gate is a reconciliation. The allocation table, the signed investor and team agreements, the contract parameters and the wallet addresses should all agree. If any bucket sits in a team multisig with no schedule, the TGE should wait until it does not.

The same rule applies to the liquidity the team seeds itself. If the project funds an on-chain pool, the pool position should be locked for a stated period, and the lock address published with the other contracts. Otherwise the market has to assume the team can withdraw the pool at any time, and some buyers will price that in.

Order matters inside this gate too. Deploy to a test network first, have someone outside the build team check every parameter against the approved table, and only then deploy to mainnet. A cliff entered in days instead of months is easy to fix on a test network and very public to fix after launch.

When should market-maker terms be signed, and on what model?

Market-maker agreements should be signed and reviewed before exchange talks conclude, because the loaned tokens are part of the launch float and the exchange will ask who is quoting. Signing them in the final week leaves no time to read them.

Two models come up most in public reporting. In a loan-and-option deal, the project lends tokens and the market maker may later buy them at agreed prices. In a retainer, the project pays a fixed monthly fee for defined services. Cointelegraph’s review of loan-option deals found that performance indicators were often missing or vague, deal terms sit behind NDAs, and all six projects it examined under such deals fell in price. It reported that retainers cost more in the short term and carry less of that risk.

There is also a conduct question. In October 2024, US prosecutors in Massachusetts charged eighteen individuals and entities, alleging that token issuers paid market-making firms to wash trade and inflate apparent volume. The charges are allegations; the release noted that some defendants had pleaded or agreed to plead guilty, and every other defendant is presumed innocent unless proven guilty. The lesson for a funded team is narrower: any agreement that pays for volume rather than measurable depth and spread is one you cannot defend later.

We would sign with at least two market makers, require written depth and spread obligations, and add every loaned token to the published circulating supply.

Which comes first: the exchange listing or the on-chain pool?

The listing date the exchange confirms should set the TGE date, not the other way round. The on-chain pool is something the team controls. The exchange listing is not.

Coinbase’s published guide to its listing process is a useful reference point. It says applying is free and merit-based, that legal, compliance and technical security reviews follow a business evaluation, and that it does not tell issuers when or whether an asset will list. It describes due diligence averaging about a week and review-to-listing generally under 30 days, with wide variation. Other venues work differently, and the market has no common timetable.

Arrakis, an on-chain liquidity provider, frames the day-one task as deploying on-chain liquidity in step with centralised listings. That is the right instinct. A pool that opens hours before the first exchange order book becomes the only price, and it may well be the thinnest one. If the exchange slips, the pool should slip with it.

What has to be filed, and how far ahead?

As of October 2026, a team that must publish a MiCA white paper to offer a token to the public in the EU, or to seek its admission to trading there, must notify that white paper to its home regulator at least 20 working days before publishing it. That is the effect of Article 8 of MiCA, which also requires a list of the host member states where the offer or listing is planned and the intended start date.

Regulators cannot require prior approval of the white paper under that article. The notification period is still a hard floor, and it runs in working days, not calendar days. It also requires an explanation of why the token is not an e-money or asset-referenced token. Counsel should own this workstream and the classification behind it. The head of markets should treat the filing date as a gate that the exchange date must sit behind.

Other jurisdictions have their own rules. The point for the sequence is the same: the filing calendar is fixed by law and cannot be compressed in the last week.

How should the sequence run, gate by gate?

The sequence should be a series of gates, each with an owner and a piece of evidence that closes it. A gate that is not closed moves the date. The table below is the order we would run for a funded project with a centralised listing and an on-chain pool.

Two habits make this work. First, the public date is announced last, after every external party has confirmed in writing. Second, the CEO holds a formal go or no-go meeting before the announcement, with the head of markets reporting on each gate. A TGE checklist for funded projects is only useful if someone has authority to stop at it.

What goes wrong: a launch plan that assumed liquidity

The plan says the token will trade at a given valuation on day one. Behind that sentence is an assumption that nobody tested: that there will be enough resting orders, on enough venues, to absorb the supply that arrives.

The assumption fails in predictable ways. The exchange date slips, but the pool is already live, so the only price is the thinnest one. The market maker received tokens without a depth obligation and sells part of them to fund its bids. Airdrop recipients and early buyers sell into the same thin book. The valuation in the deck was never a market price. It was a number the order book could not hold.

Memento’s data shows how common the result is. CryptoSlate’s report on it noted that none of the 28 launches priced at or above $1 billion were above their opening valuation, with a median decline of about 81%. Memento’s own reading was that much price discovery had already happened before TGE, so the launch often marked the top.

The defence is to treat liquidity as something measured before the date, not assumed in the plan. The head of markets should know, in writing, who will quote, how deep, on which venues, and from what day. If those answers are not in hand, the date is not real.

How Alcyone approaches it

Alcyone runs a launch as a sequence with named owners rather than a date with a list attached. In how an Alcyone launch engagement runs, a fixed-scope assessment in week two is followed by a plan built over three to six weeks, with a named owner for every part. The launch window follows, with the same partners on the line and a post-launch report within the week. In one published case, Alcyone supported the first token launch on a major Layer-1, which added more than 5,000 new holders. Clients are under no obligation to use TrustSwap products.