VestreamAlmost every vesting schedule you'll encounter combines two primitives: a cliff (a fixed period during which nothing unlocks, followed by a lump-sum release) and a linear release (continuous or stepped unlocks over time). Used alone or together, they encode different incentive structures.
If you're designing tokenomics, the choice is consequential. If you're a token recipient, understanding which pattern your allocation uses changes how you plan around it. This guide compares the two patterns directly and helps you pick the right one for any given grant.
The Two Patterns
First, plain definitions:
- Cliff vesting: for a fixed period, zero tokens unlock. At the cliff date, a chunk unlocks at once. After that, either the full remainder unlocks or a separate linear schedule begins.
- Linear vesting: tokens unlock continuously (per-second) or in regular small tranches (e.g. monthly) from start to end, with no jump events.
Most real-world vesting is 'cliff + linear': a 1-year cliff followed by 3 years of monthly or per-second linear release. This gets the retention benefit of the cliff and the smoothing benefit of linear unlocks.
Cliff Vesting: When and Why
Cliffs solve one specific problem: making sure a recipient stays long enough to be worth granting tokens to in the first place. The classic case is the four-year team vesting with a one-year cliff inherited from Silicon Valley equity practice.
- Retention test: if you leave before the cliff, you walk away with zero tokens. This filters out short-tenure grants.
- Commitment signal: a project agreeing to a long cliff for its team signals to investors that the team is in for the long haul.
- Operational simplicity: 'no tokens for 12 months' is easier to communicate than continuous accrual math.
Cliffs alone (without a subsequent linear phase) are less common – they create cliff-day chaos when the entire allocation lands in one transaction.
Linear Vesting: When and Why
Linear vesting smooths the unlock pressure on token markets and gives recipients steady cash flow. It is the right answer when you want the recipient to plan around continuous accrual rather than discrete events.
- Smooth selling pressure: recipients claim continuously rather than dumping a monthly tranche the day it lands.
- Cash-flow predictability: contractors and team members can model their token income as a steady drip.
- No cliff-day shock: there is no single timestamp where the entire community refreshes their order books.
- Composability: downstream protocols can treat the recipient's claimable balance as a real-time stream.
Decision Matrix
Use this matrix to pick the right shape for any given grant:
| Recipient type | Recommended shape | Typical config | Why |
|---|---|---|---|
| Founders / executives | Cliff + linear | 12mo cliff, 36mo linear | Retention test plus smoothed sale |
| Engineers / team | Cliff + linear | 6-12mo cliff, 24-36mo linear | Same logic, slightly shorter |
| Seed investors | Cliff + linear | 6-12mo cliff, 18-24mo linear | Locks early-low-cost positions through key milestones |
| Public sale buyers | Linear only or none | 0-6mo linear or full at TGE | Community pressure limits long lockups |
| Advisors | Cliff + linear | 3-6mo cliff, 12-18mo linear | Reflects shorter advisory engagement |
| Grants programs | Linear | 12-24mo linear | Continuous flow matches deliverable cadence |
| DAO contributors | Linear | 12mo linear, no cliff | Reward ongoing work, not tenure proof |
| Ecosystem incentives | Cliff or no vest | 0-6mo cliff or vested airdrop | Short cliff prevents instant dumping |
Protocol Support
Not every vesting protocol supports both patterns equally. Here is the rough lay of the land:
| Protocol | Cliff supported | Linear supported | Tranched alternative |
|---|---|---|---|
| Sablier (LockupLinear) | Yes (inline param) | Yes (per-second) | LockupTranched |
| Hedgey | Yes | Yes | Yes (period-based) |
| UNCX (TokenVesting v3) | Yes (via emission delay) | Yes (linear between two timestamps) | No |
| Superfluid | Yes (separate cliff transfer) | Yes (post-cliff flow) | No |
| Streamflow | Yes | Yes | Yes |
| PinkSale (PinkLock V2) | Yes (TGE percent) | Cycle-based | Yes |
Every modern vesting protocol supports cliff plus linear in one form or another. The meaningful differences are about the underlying contract architecture and how unlocks are surfaced to the user, not whether the pattern is supported at all.
Communicating Vesting to Your Community
Whatever shape you pick, the most common reason a vesting schedule generates community backlash is poor communication, not the schedule itself. A few tactics that help:
- 1Publish the schedule as both a chart and a table – different audiences read different formats.
- 2List unlock dates explicitly. 'Q3 2026' is fine; '92 days from TGE' is better.
- 3Disclose the underlying protocol and contract address. Anyone should be able to verify your schedule on-chain.
- 4If you change anything mid-flight (e.g. extend a cliff voluntarily), publish the new schedule the same way.
Tracking Vesting Across Protocols
Vestream normalises cliff dates, linear release rates, and tranche events into one dashboard across Sablier, Hedgey, UNCX, Superfluid, Streamflow, and more. Sign in at <a href="/login">Vestream</a> to compare schedules side by side.
FAQ
Frequently Asked Questions
Is cliff vesting always better than linear?
No. Cliffs are a retention test – they only make sense when continued contribution from the recipient matters. For investors, smaller cliffs plus longer linear is often a better fit.
Can I have multiple cliffs in one schedule?
Most protocols support only a single cliff. If you need multiple cliffs, you typically chain multiple separate vesting positions or use a tranched product like Sablier's LockupTranched.
What's the standard cliff length?
12 months for founders and team, 6 months for advisors, 6-12 months for seed investors. Shorter cliffs (3 months) are common for community contributors.
Do cliffs reduce sell pressure?
They concentrate it. Without subsequent linear release, a cliff produces a single 'cliff day' of intense selling. Pair every meaningful cliff with a long linear tail to smooth this out.