How to Read a Token Unlock Schedule Before You Buy

Before you buy a token, find out how many more of them are coming. The unlock schedule tells you, and most buyers never open it. They see a price and a market cap and assume today's supply is the supply that'll exist next year. Often it isn't. Sometimes it's half.

Here's how to read a schedule, how to spot a cliff versus linear vesting, and how to turn an allocation table into a rough forecast of circulating supply. Then comes the harder question: if everyone can see these dates, do they still move the price?

What an unlock schedule actually is

Most tokens don't come out fully released at launch. The project mints a fixed total supply and hands most of it to insiders: the team, early investors, advisors, a treasury, and an ecosystem or grants fund. Those tokens sit locked, either in a smart contract or under a legal agreement, and trickle out on a schedule.

Three numbers matter:

• Circulating supply: tokens that can be traded right now.
• Total supply: everything that's been minted, locked tokens included.
• Max supply: the hard cap, if there is one. Some tokens also mint new supply through staking rewards, and that lands on top of any unlocks.

Market cap uses circulating supply. Fully diluted valuation (FDV) uses total or max supply. When circulating is a small slice of total, the gap between the two is big, and that gap is future selling capacity sitting on a calendar.

Cliff vs. linear: two very different shapes

Vesting comes in two basic forms. Most schedules mix them.

A cliff is a waiting period where nothing is released, then a lump. A typical team allocation might have a 12-month cliff and release a quarter of its tokens on the first anniversary. Nothing on day 364. A big block on day 365.

Linear vesting releases tokens in equal slices over a set period, usually monthly, sometimes daily or even per block. An ecosystem fund vesting linearly over four years adds the same modest amount every month.

The common hybrid is a cliff followed by linear vesting: wait a year, release a chunk, then drip out the rest monthly. Investor and team allocations almost always look like this.

Shape matters because markets swallow trickles far more easily than floods. Adding 3% to circulating supply every month is a headwind. Adding 40% in one day is an event. Both can deliver the same number of tokens over a year and still hit the order book in completely different ways.

Where to find the schedule

Start with the project's own docs. Look for a page called tokenomics, token distribution or allocation. A decent one gives you each bucket's percentage, cliff length, vesting length and any amount released at launch (often called TGE, the token generation event).

Then check it against other sources. Token unlock trackers aggregate schedules for larger projects. Block explorers show the vesting contracts and the wallets holding locked tokens. If the docs claim the team has a one-year cliff but the team wallet is already shipping tokens to exchanges, the docs are wrong. Or someone found a way around them.

Can't find a schedule at all? That's information too. You can't judge the supply risk, and that should count against the token.

Step by step: build the supply curve yourself

No special software needed. A spreadsheet and fifteen minutes will do it.

1. List every allocation bucket with its share of total supply: team, investors, advisors, ecosystem, treasury, public sale, liquidity, airdrop. Confirm the percentages add up to 100. If they don't, find out why.
2. Convert percentages to token counts. Multiply each share by total supply.
3. Record four terms for each bucket: amount released at launch, cliff length in months, amount released at the cliff, and the length of the linear period after it.
4. Calculate the monthly linear amount for each bucket: tokens still to vest after the cliff, divided by the number of vesting months.
5. Build a month-by-month table. One row per month from launch, one column per bucket. Add a total circulating column.
6. Add a column for monthly change as a percentage of the previous month's circulating supply. This is the number that counts. Ten million tokens means nothing until you know whether it's 3% or 40% of what's already trading.
7. Flag discretionary buckets separately. Treasury and some ecosystem funds can be spent whenever governance or the team decides. Show them as a range, not a line.
8. Mark where you are today and look 3, 6 and 12 months ahead. Write down the biggest single-month jump coming up and the total supply growth over the next year.
9. Compare upcoming releases to trading volume measured in tokens, not dollars. If a cliff releases more tokens than trade on a typical day, even a fraction getting sold is a lot for the market to absorb.

Worked example: a hypothetical token

All numbers here are hypothetical and chosen for illustration. Picture a token called EXMPL with a total supply of 1,000,000,000 and this allocation:

Launch circulating supply is 150M, or 15% of total. Run the table forward and you get this:

Read it slowly. For eleven months, supply grows roughly 3-4% a month. That's real dilution, but steady. Then month 12 dumps almost half of everything already trading, all at once. After that, the combined investor and team drip runs at 16.67M a month, more than double the first year's pace, until investor vesting finishes at month 36.

Now the treasury. If governance releases all 150M at some point, final circulating supply hits 1B. Someone who bought at launch was holding 15% of the eventual supply, and probably thought they held most of it.

To estimate month-12 selling, guess what share of recipients sell. Say 20% of the 100M cliff gets sold in the first few weeks. That's 20M tokens. If EXMPL typically trades 25M tokens a day, that's close to a full extra day of volume shoved in one direction. If it trades 200M a day, the market barely blinks. Same release, very different impact.

Do unlock dates actually predict selling?

Here's the uncomfortable part. Unlock schedules are public. Trackers publish countdowns. Anyone with an internet connection knows month 12 is coming. In a perfectly efficient market, that information would already be in the price, and the date itself would be a non-event.

Crypto markets aren't perfectly efficient, but they aren't dumb either. What tends to happen is messier than either crash-on-the-date or nothing-happens.

Selling moves earlier. Traders who expect weakness short ahead of the date or simply stay out, which pushes the pressure into the weeks before. Recipients with access to perpetual futures can hedge before their tokens release, locking in a price before they ever touch the tokens. By the time the date arrives, much of the move may be done.

The date is known. The selling isn't. Nobody outside knows how much recipients will dump. That depends on things you can partly estimate:

• Cost basis. Seed investors who paid a small fraction of the current price are sitting on huge paper gains and fund timelines to meet. They're likelier to sell than a team that still believes in the project.
• Recipient type. Ecosystem grants often go to builders who need to cover costs, so those tokens get sold. Team tokens may be restaked or held for governance.
• OTC deals. Large holders sometimes sell in private deals at a discount. The buyer then sells into the market over weeks, so the pressure is real but spread out and hard to see.
• Market conditions. A cliff in a strong market can get absorbed with barely a dip. The same cliff in a thin, falling market can be brutal.

So here's the honest answer. Unlock dates tell you supply will be available, and they flag windows where risk is concentrated. They don't reliably predict a price drop on a given day, because traders front-run them and recipients behave differently. The steady linear drip is arguably the more underrated risk. It gets less attention, and it keeps going whether anyone's watching or not.

Common mistakes

• Measuring against total supply instead of circulating. A release that's 5% of total supply sounds small. If only 20% is circulating, it's a 25% increase in what can actually trade.
• Fixating on one date. The big cliff gets the headlines. The cumulative curve over the next year matters more, and it's often dominated by monthly drips.
• Ignoring discretionary buckets. Treasury, foundation and reserve wallets can move whenever the controllers decide. No schedule doesn't mean no supply.
• Forgetting emissions. Staking rewards and liquidity incentives mint new tokens on top of any vesting. A token can finish vesting and still be inflating.
• Assuming locked means locked. Some locks are just a promise, or a multisig wallet that governance can change. Check whether a contract enforces the vesting, and whether that contract can be upgraded.
• Assuming every unlocked token gets sold. It doesn't. Model a range, say 10%, 25% and 50% sold, and see whether your thesis survives the high end.
• Comparing in dollars instead of tokens. Price swings distort dollar comparisons. Compare release size to daily volume in token units.

Applying this before you buy

This matters most for short and medium holding periods, which covers a lot of trading and a lot of the tokens tied to gambling platforms and their rewards programs. Plan to hold a few months? Look at what happens in those months. If a cliff lands inside your window, you're betting that it's priced in or that demand will absorb it. Either can be right. Just know which bet you're making.

A clean schedule doesn't make a token a good buy, and a heavy one doesn't make it a bad one. It shows you the supply side, so you can judge whether demand is likely to keep up.

FAQ

Does a big cliff always mean the price drops?

No. Some of the impact is often traded ahead of time, and sometimes the price recovers after the date once the feared selling turns out smaller than expected. A cliff raises the odds of pressure around that window. It doesn't guarantee a drop on the day.

What's the difference between an unlock and vesting?

Vesting is the schedule, the full timeline over which tokens become available. An unlock is any single release event within it. A linear schedule produces many small releases. A cliff produces one large one.

Can a project change its unlock schedule?

Sometimes. If a contract that can't be changed enforces the vesting, no. If tokens sit in a multisig wallet or the terms depend on governance, the schedule can be extended, which usually reassures holders, or accelerated, which usually doesn't. Check the contract, not just the docs.

The schedule is the easy part, since it's written down. What you can't read off it is who's on the other side of each release and what they paid. Next time a cliff approaches, ask that before you look at the countdown.