Guide
Reading a Token Unlock Schedule: Cliffs, Linear Vesting and Why Dates Slip
How to read a vesting chart like an analyst rather than a marketing slide, including why the published unlock date is often an estimate, not a guarantee.
A vesting chart looks simple on a pitch deck: a line that climbs from zero to one hundred percent of an allocation. In practice, that line is a summary of a contract (or a set of chain-level rules) with its own edge cases, and the published date on a tracker site is usually someone’s best estimate of when that contract fires, not a certainty. Reading a schedule properly means knowing what a cliff and linear vesting actually do, where the real terms live, and why the calendar date you see today might not be the date that actually happens.
What a vesting schedule is describing
A vesting schedule describes when previously allocated but locked tokens become transferable — it is not describing new issuance from a mint function. The tokens already exist in a technical sense; they are counted toward total or max supply, and sometimes they are visible on-chain sitting in a vesting contract address. What vesting controls is whether they count as circulating supply: tradable, sellable, deliverable to an exchange. That distinction matters because a large unlock does not create new tokens out of nothing — it moves existing tokens from a locked state into the available float, which is a very different event from, say, a staking reward or a block reward.
Cliffs: a single release after a waiting period
A cliff is the simplest unlock structure: nothing unlocks for a defined period, and then a chunk unlocks at once, often the entire allocation assigned to that cliff or the first installment of a longer schedule. Teams use cliffs for early contributors and investors to keep them aligned with the project for a minimum period before any of their tokens can reach the market. The analytical point to flag: a cliff concentrates supply impact into a single date. If you are tracking an asset through a known cliff, that date deserves more attention than a routine linear release of comparable size, because the whole amount can hit the float at once rather than trickling in.
Linear vesting: the same supply, spread out
Linear vesting releases a fixed amount (or a fixed percentage of the remaining locked balance) on a recurring basis — daily, weekly, or monthly — over a defined duration. It is often layered after a cliff: for example, a one-year cliff followed by three years of monthly linear release. The total amount unlocked is identical to a cliff-only design with the same allocation; what changes is the shape of the release. Spreading an unlock across many small events generally makes each individual event less disruptive to read in isolation, but it also means the schedule keeps adding to circulating supply every month for years, which is easy to lose track of once the initial headline cliff has passed.
Where the real schedule actually lives
Marketing pages and unlock-tracker sites summarize a schedule, and summaries drift from source documents for mundane reasons: a team updates docs after a governance vote and a third-party tracker does not catch the change, or a visualization rounds dates to the nearest month. For a token with an on-chain vesting contract, the contract’s own code and its transaction history are the ground truth — you can usually see the unlock function, the schedule parameters it was deployed with, and every actual release transaction it has executed so far. For assets without a public smart contract (native-chain allocations, for instance), look for the protocol’s own release notes or governance records rather than relying on a single aggregator’s chart. When this site references an unlock, the unlocks calendar links back to the sourced calendar entry for that event rather than restating a number with no origin.
Why published unlock dates slip
Four mechanisms account for most date slippage, and none of them require anyone to break a contract:
- Admin-controlled extensions. Some vesting contracts are deployed with an owner function that can delay the schedule, often framed as a safeguard against short-term sell pressure. If that function exists, the “schedule” is partly a policy choice, not purely code.
- Governance votes. Token holders or a foundation council can vote to extend lockups, a tool some projects have used explicitly to manage market conditions around a large release.
- Contract migrations. A project moving to a new token contract, a new chain, or a new vesting vendor can reset or restate a schedule in the process, intentionally or as a side effect.
- Simple restatement. Teams sometimes revise an original schedule in a blog post without changing any contract, because the original figures were provisional (for example, tied to a token generation event date that had not yet happened when the schedule was first published).
None of this means every project manipulates its schedule. It means a calendar date on a tracker is an input to your analysis, not a settled fact, until the release transaction is actually visible on-chain.
A worked example of reading a schedule
Take a hypothetical allocation of 60,000,000 tokens assigned to an investor round, with a 12-month cliff followed by 24 months of equal monthly linear vesting. At the cliff date, 60,000,000 / 25 = 2,400,000 tokens unlock at once (treating the schedule as 25 equal installments: the cliff plus 24 months), and then 2,400,000 more unlock each month for the following 24 months. If the token’s circulating supply at the cliff date is 400,000,000, that single cliff event adds 0.6% to circulating supply in one day. Each subsequent monthly release adds the same absolute amount against a circulating supply that is itself growing from prior releases, so the percentage impact of each monthly unlock actually shrinks slightly over time even though the token count released stays flat. This is the same calculation this site’s guide on sizing an unlock against circulating float walks through in more depth, and the dilution-maths guide covers how to annualize the result.
What to watch going forward
Treat a published schedule as a hypothesis to monitor, not a fact to file away. Check whether the allocation address has moved tokens ahead of its stated date (a sign the schedule changed or an early distribution occurred), check governance forums for any vote touching vesting terms, and compare the tracker’s current version of the schedule against the version it showed months ago if an archive is available. The unlocks calendar on this site lists upcoming scheduled unlocks with a source for each row and an explicit “scheduled, may change” note, which is the honest framing every unlock calendar should carry.
Aggregator charts vs primary sources, in practice
Third-party unlock trackers are genuinely useful for getting a first read on an asset’s schedule across many projects at once, which is harder to do by hand across dozens of individual contracts. The trade-off is that an aggregator has to normalize many different contract structures into one chart format, and normalization is where small distortions creep in: a project with an unusual multi-tranche structure might get simplified into a single linear line that is close but not exact, or a schedule denominated in a non-standard period might get rounded to the nearest month. None of this means aggregators are unreliable in general — it means treat an aggregator’s chart as a strong starting hypothesis, and reach for the primary contract when a specific date or amount is about to matter for a decision, exactly as you would fact-check any other secondary source.
Edge cases that complicate a schedule
A few structural situations are common enough to flag on their own. A token swap or migration to a new contract can reset the apparent vesting clock in a tracker that keyed its data to the old contract address, even if the underlying economic terms did not actually change. A bridge wrapping a token on a second chain for liquidity purposes can create a second address with its own balance that has nothing to do with the vesting contract on the home chain, which can confuse a naive “check the balance of this address” approach to verification. And a schedule denominated in a stablecoin-equivalent value rather than a fixed token count — rare, but it exists in a few designs — means the actual number of tokens released on a given date can vary with price, which is a meaningfully different thing to track than a fixed-count schedule. None of these are reasons to give up on verification; they are reasons to read the specific contract’s terms rather than assume every vesting schedule works exactly like the simplest textbook case.
Risk note
An unlock is a supply-side event, not a verdict on an asset’s future price. Markets sometimes absorb large unlocks with little visible effect and sometimes react sharply to small ones, depending on factors well beyond the schedule itself. Use this guide to understand the mechanism, not to time a trade around a date.
Not financial advice. This guide explains how supply mechanics work so you can read them yourself; it does not recommend buying, holding, or selling any asset, and none of the worked numbers in this guide are live market data.
Frequently asked questions
What is a vesting cliff in crypto tokenomics?
A cliff is a period during which zero tokens unlock, followed by a release of a lump sum (often the full cliff allocation at once) on a single date. It is used to keep early contributors committed for a minimum period before any of their allocation becomes liquid.
Why do unlock dates sometimes change after they are published?
Smart contracts can include admin functions that let a foundation extend a lockup, a governance vote can approve a schedule change, or a project can migrate tokens to a new contract with different terms. None of these require breaking the original contract outright, which is why slippage is more common than most summaries suggest.
Is linear vesting safer for holders than a cliff?
It spreads the supply impact over time rather than concentrating it on one date, which generally makes individual releases smaller relative to circulating float. That is a different risk profile, not an automatically safer one -- a long linear schedule still delivers the same total supply eventually.
Where is the authoritative source for a vesting schedule?
The deployed vesting or token contract itself, or the chain-native equivalent for a non-smart-contract network, is the authoritative source. Docs, blog posts and third-party unlock trackers are summaries of that source and can lag or simplify it.
Not financial advice. Ecoin Supply describes how crypto-asset supply works and what public sources report. Crypto-assets are volatile and you can lose all of the money you put in. Nothing on this site is a recommendation to buy, sell or hold any asset, and no figure here is a price prediction.