VestreamAsk most crypto investors what a vesting cliff is, and they will tell you it is 'a waiting period before tokens unlock.' That is technically correct, but it misses what makes the cliff structurally significant. The cliff is not just a delay – it is a concentrated release event that can deliver 12 to 24 months' worth of token allocation in a single transaction. Understanding the cliff at a mechanical level changes how you analyse a project's tokenomics and how you position around unlock events.
This article covers cliff mechanics in depth: what they are, how they are encoded in smart contracts, why they became standard practice, the market dynamics they generate, and how to identify cliff events before they arrive. By the end, you will be able to read any vesting schedule and quickly determine whether the cliff presents a risk, an opportunity, or a non-event.
What Is a Vesting Cliff?
A vesting cliff is a period at the start of a vesting schedule during which zero tokens are released. Once the cliff date is reached, a pre-defined lump sum – typically corresponding to the proportion of the total allocation that 'accrued' during the cliff period – unlocks immediately. After the cliff, remaining tokens vest according to the ongoing schedule (usually linear).
The classic structure in crypto is: 12-month cliff, 36-month total vest. Under this schedule, 1/3 of the total allocation unlocks on the one-year anniversary of the grant date. The remaining 2/3 then vests linearly over the following 24 months, releasing in monthly increments. This is borrowed directly from startup equity compensation, where the same structure has been standard since the 1980s.
Without a cliff, linear vesting begins from day one – the recipient earns tokens continuously from grant date. With a cliff, nothing is earned (or at least nothing is withdrawable) until the cliff date, at which point all accrued tokens release at once. The cliff is a threshold, not a gradual ramp.
How Cliff Calculations Work On-Chain
On-chain, a cliff is implemented by comparing the current block timestamp to a stored cliff timestamp. Before the cliff, withdrawal functions revert with a 'cliff not reached' error. After the cliff, the claimable amount includes the cliff allocation.
Different protocols model cliffs differently. In Sablier v2 LockupLinear, two separate amounts are specified: a cliff amount (released at the cliff timestamp) and a streaming amount (released linearly from cliff to end). This allows precise control – a 25% cliff with 75% linear, for example, or a 0% cliff with 100% linear.
In UNCX, the cliff is modelled as a single timestamp before which nothing vests. After the cliff, the contract calculates how many full periods have elapsed since the start and releases the proportional amount. Some implementations allow multiple cliff stages – a cascading cliff where partial amounts release at defined intervals before the full schedule begins.
- Cliff timestamp precision: Cliffs are encoded as Unix timestamps (seconds since January 1, 1970). The practical precision is one second, but actual block timestamps vary by chain – Ethereum blocks target 12 seconds, making cliff execution within 1–2 blocks of the target timestamp.
- Discrete vs continuous models: Streaming protocols (Sablier) release tokens continuously, so the 'cliff event' is technically the moment streaming begins rather than a discrete batch release. Non-streaming protocols release a fixed amount at the cliff block, making the event more discrete and visible on-chain.
- Gas and execution: The cliff release does not happen automatically. Recipients must call a claim or withdraw function. This means the actual on-chain transfer may happen hours or days after the cliff timestamp, depending on recipient attention and gas prices.
Why Cliffs Exist
The cliff serves three distinct functions, each of which is relevant to how you evaluate a project's tokenomics design:
- 1Commitment signalling. A cliff creates a minimum tenure requirement: recipients must stay engaged with the project for at least the cliff duration to receive any tokens. For team members, this is a retention mechanism. For investors, it is a signal that they are committing to the project's trajectory rather than looking for a quick exit.
- 2Anti-dump protection. Without a cliff, linear vesting begins on day one. For a token that is newly listed, early investors could immediately begin selling their first month's vesting allocation. The cliff delays this entirely, giving the token time to establish market depth and price discovery before meaningful selling from insiders begins.
- 3Alignment with project milestones. In practice, the 12-month cliff roughly corresponds to the time it takes for a project to launch its mainnet product, build early community, and establish some track record. Releasing tokens before this milestone would be premature for all parties.
The 12-month cliff in crypto traces directly to Silicon Valley startup equity. Typical startup equity grants use a 4-year vest with 1-year cliff – the same '1+3' or '1+2' structures common in crypto. When the first token-compensated crypto projects structured their allocations, they borrowed from equity compensation norms. The structure stuck, even though the liquidity dynamics of tokens are fundamentally different from illiquid startup equity.
The Cliff Release Problem
Here is where the cliff becomes a market structure event rather than just a schedule mechanism. When the cliff fires, a large discrete quantity of tokens – potentially 20–35% of total allocation – becomes immediately liquid. The size of this event relative to the existing circulating supply determines whether the cliff is a market-moving occurrence or a non-event.
| Unlock Type | Market Impact Profile | Price Predictability | Seller Incentive |
|---|---|---|---|
| Cliff release | Large discrete shock on cliff date | Low (single-day event, hard to predict timing) | High pressure if cost basis well below market |
| Linear monthly | Steady incremental supply addition | High (predictable monthly amounts) | Moderate – small per-event, but cumulative |
| Quarterly tranches | Medium discrete events 4× per year | Medium | Moderate – larger than monthly, smaller than cliff |
| Continuous stream (Sablier) | Per-second micro-additions | Very high (fully predictable) | Low per-moment, but meaningful on long timescales |
Sophisticated market participants – particularly those with access to vesting schedule data – often begin positioning before the cliff date. This typically manifests as increased short interest, reduced buy-side depth, or direct selling by recipients who hold pre-cliff positions through derivatives or OTC agreements. The result is that many cliff events show price weakness in the 7–14 days before the cliff fires.
Cliff Variations in the Wild
Not all projects use the standard 12-month cliff. Here is a taxonomy of cliff structures and what they signal about a project's incentive design:
- No cliff (fully linear from day one). Common for community allocations and public sale tokens. Signals that the project wants recipients to feel immediate ownership. Watch for projects claiming 'no cliff' for team and investor allocations – this is a yellow flag for commitment.
- Short cliff (3–6 months). Used when liquidity is needed quickly – bootstrapping liquidity provider incentives, early ecosystem grants. Appropriate for operational allocations, but concerning for investor/team tokens.
- Standard cliff (12 months). The baseline. Reasonable alignment signal. Evaluate based on total vesting duration: a 12-month cliff with 14-month total vest is almost as risky as no cliff. A 12-month cliff with 36-month total vest is genuinely aligned.
- Extended cliff (18–24 months). Strong commitment signal, particularly for founding teams. Rare but increasingly seen in 'long-term narrative' projects that want to communicate multi-year conviction.
- Back-loaded schedules. Some projects use a reverse-cliff structure: small early tranches that increase in size over time. This discourages early selling but creates growing supply pressure in later years.
How to Find and Track Cliff Dates
Identifying cliff dates for tokens you hold or are researching requires reading the vesting contract data directly. The process varies by protocol:
- 1Find the vesting contract address. The project's documentation, tokenomics page, or initial token deployment transaction should reference the vesting contract. Many projects post this on their website or GitHub.
- 2Read the contract storage. Using a block explorer (Etherscan, BscScan, etc.), navigate to the contract and call the read functions. Look for
cliffTime,cliffDate,vestingStart, or equivalent variables. - 3Use a vesting aggregator. Tools like Vestream index vesting contracts across Sablier, UNCX, Hedgey, and Unvest, surfacing your cliff dates and unlock calendar in a single dashboard without manual contract interrogation.
- 4Verify against tokenomics documentation. On-chain data is ground truth, but project documentation often explains the intent behind the schedule. Discrepancies between documented schedules and on-chain data are a significant red flag.
Frequently Asked Questions
What happens to unvested tokens during the cliff period?
During the cliff period, tokens remain in the vesting contract – they are not accessible to the recipient or the project. The project deposited them at vesting schedule creation; neither party can access them until the cliff date. If the schedule is revocable, the project can cancel the schedule and recover unvested tokens, but cannot access them without cancellation.
Can a cliff be modified or removed after vesting has started?
Generally no. Vesting schedules in smart contracts are largely immutable once created. The cliff timestamp is written into the contract at deployment and cannot be changed without deploying an entirely new vesting contract. Some multi-sig controlled contracts allow parameter modification, but this requires transparent governance and is rare in practice.
Do all tokens have vesting cliffs?
No. Public sale tokens and community distribution tokens often have no cliff – they vest immediately or on a short linear schedule. Mining and staking rewards typically have no cliff at all. Cliffs are most common for team, investor, and advisor allocations where long-term alignment is the goal. Always check the specific allocation category you are tracking.
What is a 'hard cliff' vs 'soft cliff'?
In some documentation, a 'hard cliff' refers to a schedule where zero tokens are accessible before the cliff date regardless of circumstances – the smart contract enforces it unconditionally. A 'soft cliff' sometimes refers to a revocable schedule where, while tokens don't vest before the cliff, the depositor can cancel the schedule and change the terms. In strict technical usage, all on-chain cliffs are 'hard' (the contract enforces them), but the revocability of the overall schedule affects the practical security of the recipient's allocation.
Can I sell or transfer my vesting position before the cliff fires?
On protocols that represent vesting as NFTs (Sablier, Hedgey), you can transfer the vesting NFT to another address, effectively selling the future claim to the tokens. The new holder then waits for the cliff and claims. On address-locked protocols (UNCX, Unvest), you cannot transfer the vesting position – it is permanently tied to the recipient address set at creation.