Sync Contact us

Build and operateUpdated August 2026

Token Unlock Schedules: The Document Everyone Reads and Nobody Writes For

Your unlock schedule is read by every exchange desk, fund and integration partner assessing you. Most are written for investors and reviewed by people who are not investors.

A token unlock schedule sets out who receives tokens, how many, and on what dates after launch. It is written for investors, negotiated with investors, and then read almost exclusively by people who are not investors: exchange trading desks, listing committees, integration partners and institutional buyers, all of whom are asking a different question from the one it was drafted to answer.

That mismatch is the whole problem. The schedule gets designed to satisfy a cap table and then gets graded by a trading desk, and the desk is not reading it for fairness. It is reading it for supply risk, and it does that whether or not you present the schedule at all.

Here is the position worth arguing with: for most projects, the unlock schedule does more damage to a listing than the product ever does. A large tranche landing close to launch is read as an exit, and no amount of relationship work at the venue overrides it, because the person who reaches that conclusion is not the person you have the relationship with.

One disclosure before the argument. Sync works on go-to-market and listings, not on your cap table, and we are not lawyers or advisers on the terms themselves. What follows is about how the document is read by the counterparties we deal with, which is a narrower and more useful thing than advice on what your allocations should be.

Who actually reads it, and what each of them is looking for

The exchange trading desk models the schedule as forward supply. It wants to know how much sell pressure arrives, when, and whether the market-making arrangement can absorb it. This is the reader that matters most and the one least likely to speak to you directly.

The listing committee wants to know whether approving you creates a problem in three months. Binance’s published delisting guidelines list “poor liquidity, low market capitalization” under market risk (Binance Support), so a schedule that predictably thins the book is a schedule that predictably triggers the review the committee is trying to avoid.

Counsel, on both sides. The allocation structure interacts with how the token is treated. Since 17 March 2026 a written regulatory position has to engage with the joint SEC and CFTC interpretation, release 33-11412, which expressly superseded the SEC staff’s 2019 Howey framework for digital assets (SEC). A schedule drafted against the old framework, or a SAFT structured around it, dates the whole pack.

Institutional buyers, who read it as counterparty risk rather than as an investment term. The wider diligence pack they run is in the compliance pack an institutional buyer asks for.

The four things that get a schedule marked down

  1. Any single unlock whose value exceeds three to five days of average trading volume. That is the absorption threshold crypto.news sets out in its explainer of unlocks, vesting and cliffs, published 15 July 2026: above it, absorption is slow and the price does the absorbing. It is a better test than a percentage of supply because it is the one the trading desk is actually running.
  2. A cliff that lands within two weeks of a major unlock elsewhere in the schedule. Two events close together get modelled as one larger event, so the stacking undoes the benefit the staging was meant to buy.
  3. Any allocation without a named recipient category and a dated release. “Ecosystem” with no schedule is read as discretionary supply, which is the least reassuring thing a line item can be.
  4. A schedule that changed after the last public version, without the change published. This one is fatal in a way the others are not. It converts a supply question into a trust question, and trust questions do not get resolved by better tokenomics.
  1. 01 Above the absorption threshold A single unlock worth more than three to five days of average volume
  2. 02 Stacked events A cliff within two weeks of another major unlock, modelled as one larger event
  3. 03 Unnamed allocation No recipient category and no dated release, read as discretionary supply
  4. 04 A silent change Changed since the last public version without publishing the change Fatal, and not a tokenomics problem
Four failures a desk marks down, and the last one is different from the others.

What the conventional schedule looks like

Worth knowing before you deviate from it, because deviation is what gets questioned. The common shape is a cliff of six to twelve months after the token generation event during which nothing releases at all, and for team allocations a one-year cliff followed by monthly unlocks over the two or three years after it (crypto.news, published 15 July 2026). Investor allocations usually vest faster than team allocations.

A schedule inside that shape does not need defending. One outside it does, and the defence has to be written down before somebody asks.

You can pass one of these tests and fail the other

This is the part worth reading twice, because you can pass one of these tests and fail the other with the same schedule.

The absorption rule above is expressed in days of trading volume: keep any single unlock under three to five days of average volume and the market can take it. Tokenomics.com, in its argument against linear unlocks published 22 June 2026, uses a completely different measure - float at launch - and reports that the best-performing projects show 15.18% initial circulating supply against 4.98% for a typical launch.

Those two are not the same test and they can point opposite ways. A high float satisfies the second benchmark and can still put an unlock through the first one, because a larger circulating supply does not guarantee the volume to absorb the next tranche. A low float protects the first test by keeping unlocks small in absolute terms while failing the second outright.

Neither source reconciles with the other, and neither cites a dataset you can inspect. What you will actually be judged on is the volume test, because that is the one a trading desk runs before it quotes. Treat the float benchmark as a design input and the absorption rule as the pass mark.

An unlock schedule is really a credibility document

A token unlock schedule is really a credibility document that happens to contain numbers, and the numbers are the smaller half.

The reason is that everything in it is checkable and permanent. Anyone can read what you committed to and compare it to what happened, forever, on chain. Almost nothing else a crypto project publishes has that property. Your marketing claims decay, your team page changes, your roadmap slips and is quietly rewritten. The unlock schedule is the one artefact where a counterparty can grade your word against a public record, and they know it.

That is why publishing a slightly worse schedule you will actually keep beats publishing an attractive one you will have to amend. The amendment is the event people remember.

Getting the schedule and the liquidity plan into the same conversation

These are usually built by different people at different times, and that is where most of the damage happens.

The market-making agreement commits to a quoted spread and a depth. The unlock schedule determines how much supply arrives against that depth and when. Sign the first without modelling the second and you have agreed to defend a book against volume nobody sized. Market makers, Wintermute, GSR, Keyrock and Flowdesk among the names that recur, will model it themselves before quoting, so the only party surprised by the interaction is usually the project. The gate sequence this feeds into is set out in the five gates a listing has to pass.

The same schedule then drives the quarter after launch, when attention decays in days and volume over weeks, and the monthly exchange review starts grading you. That period is covered in what happens after a token listing.

What we would fix first

  1. Model the first four unlock events against your committed market-making depth before you sign either. If the arithmetic does not work, one of the two documents is wrong and it is cheaper to find out now.
  2. Price every unlock event against three to five days of your expected average volume, and move anything above it. This is the one rejection you can fix with a spreadsheet rather than a quarter of work, and it is arithmetic rather than judgement.
  3. Give every allocation a named category and a date, including the ecosystem line. Undated supply is the line item a desk assumes the worst about.
  4. Publish the schedule once and change it never. If it must change, publish the change and the reason on the same day, because the alternative is that somebody else finds the discrepancy and publishes it for you.

How Sync works on a schedule

We do not draft your tokenomics or advise on allocations. What we do is the part that sits between the schedule and the market: how it is presented to a venue, how it interacts with the liquidity arrangement, and what the quarter after launch has to look like for the monthly review to go well. That work opens with an audit of what already exists, then a discovery call, a proposal, and a written strategy you sign off before anything is spent. About Sync sets out the way we work and the people who agreed to act as references for it.

FAQ

What is a token unlock schedule?

The dated plan for when locked tokens become transferable, and to whom. It is drafted as a term for investors and team, and then read by exchange trading desks, listing committees, counsel and institutional buyers as a forecast of forward supply. Those readers are asking about sell pressure, not fairness.

How do token unlocks affect a listing?

Directly, and usually before you hear about it. A trading desk models forward supply against the depth it has committed to quote, so a large tranche landing near launch reads as sell pressure the book cannot absorb. Binance’s own delisting guidelines put poor liquidity and low market capitalisation under market risk, which is the outcome a badly staged schedule produces.

When should the first token unlock happen?

Later than most schedules put it. The testable rule is value rather than date: keep any single unlock under three to five days of average trading volume, which is the absorption threshold crypto.news sets out and the one a trading desk is effectively running. Beyond that, spacing matters - two events within a fortnight get modelled as one larger event, which undoes the benefit the staging was supposed to buy.

Can you change a token unlock schedule after publishing it?

You can, and it costs more than the change itself is worth in almost every case. An amended schedule converts a supply question into a trust question, and trust questions are not resolved by better tokenomics. If it has to change, publish the change and the reason on the same day rather than letting somebody else find the discrepancy.


Related: Web3 business development, defined · How to get listed on a crypto exchange · What happens after a token listing · Selling crypto to institutional investors · How partnership deals actually get closed · Crypto exchange marketing

Written by Sync, a Web3 marketing and business development agency.