Token Vesting Explained: Cliffs, Unlocks, and Supply Risk

Token vesting is a schedule that determines when an allocation of crypto tokens becomes claimable or transferable by a beneficiary such as a founder, employee, investor, adviser, community program, or treasury. A vesting schedule can release tokens gradually, hold them behind a cliff, or combine both. OpenZeppelin’s VestingWallet documentation shows the core onchain idea: assets are held for a beneficiary and released according to a defined schedule. For investors, the practical question is not only when tokens “unlock,” but how much new liquid supply can actually reach the market, who controls it, and whether the published schedule matches the contract and current governance decisions.

Vesting does not automatically mean selling. An unlock creates the ability to claim or transfer tokens under the relevant rules; it does not prove that the beneficiary will send them to an exchange. That distinction is the starting point for evaluating token-supply risk without turning every calendar event into a bearish headline.

Key takeaways

• Vesting describes how an allocation becomes earned or releasable over time; a lockup can impose an additional restriction even after vesting.
• A cliff is a period during which no scheduled amount is claimable, or during which accrued vesting cannot be claimed, depending on the contract design.
• “Unlocked,” “vested,” “circulating,” “transferred,” and “sold” are not interchangeable terms.
• A large unlock matters most when it is large relative to circulating supply and market liquidity, and when recipients have both the ability and incentive to sell.
• Linear, stepped, milestone-based, and cliff schedules can produce very different supply paths even when the same total allocation is involved.
• Smart contracts can make schedules auditable, but contract ownership, migrations, revocation rights, rebase behavior, and transferable claims can change the real economic exposure.
• Fully diluted valuation can make a low-float token look expensive, but FDV alone does not tell you when supply will arrive or whether recipients will sell.
• The safest workflow is source-first: project allocation documents, vesting contracts, onchain balances, governance changes, and then independent market data.

What is token vesting?

Token vesting is a restriction on when a beneficiary gains access to an allocation. Projects use it to align contributors with a longer time horizon, prevent an entire insider allocation from becoming liquid on launch day, or structure grants around employment and milestones.

The mechanism can be contractual, legal, operational, or a combination of all three. An ERC-20 allocation might sit in a vesting contract that calculates how much is releasable at any timestamp. A foundation may hold tokens in a multisig and follow a publicly announced schedule. An employee grant may vest under an offchain agreement while the actual tokens remain subject to another lockup. These arrangements have different verification standards.

OpenZeppelin’s implementation allows a vesting wallet to hold native currency and ERC-20 tokens and release them according to a customizable schedule. The documentation also highlights an important edge case: if assets are added after the schedule has already started, a portion may be immediately releasable because the contract treats them as if they had been present from the beginning. That is why a vesting address should be analyzed together with its code and funding history rather than only with a marketing chart.

Vesting vs lockup vs unlock

These terms often appear together but answer different questions.

A project can therefore report a grant as vested while a separate transfer restriction remains. Conversely, a token can move between controlled wallets without becoming meaningful public float. Treating every wallet movement as “selling” overstates evidence.

This distinction also matters when smart contracts are involved. BTC-Pulse’s guide to smart contract wallets explains why programmable ownership can contain recovery, upgrade, or policy logic. A vesting contract is another programmable custody layer: the economic result depends on both the schedule and who can alter, migrate, or own the relevant contract.

Common token vesting schedules

Cliff then linear vesting

A beneficiary waits through an initial cliff and then receives tokens gradually. The schedule may accrue from day one but block claims until the cliff, or it may begin linear vesting only after the cliff. Those two designs produce different amounts at the cliff date.

Pure linear vesting

The vested amount grows continuously or in frequent discrete steps from zero to the full allocation over a fixed duration. This creates a smoother theoretical supply path, although beneficiaries can accumulate claimable balances and sell later in one transaction.

Stepped unlocks

A fixed percentage becomes available monthly, quarterly, or on specific dates. A quarterly schedule creates more visible supply jumps than continuous vesting.

Milestone-based vesting

Tokens become available after a deliverable, governance milestone, financing event, network launch, or other condition. Investors should verify who certifies the milestone and whether the condition can be changed.

Hybrid schedules

Projects often combine a cliff, an initial tranche, monthly vesting, and separate rules for team, investors, ecosystem incentives, and treasury allocations. A single “next unlock” number can hide these bucket-specific differences.

The Ethereum community has explored standardized interfaces as well. ERC-5725, currently Final, extends ERC-721 with transferable vesting NFTs representing underlying tokens, including ERC-20 tokens, released over a vesting curve. ERC-7720, currently Draft, proposes a separate interface for ERC-20 deposits that a beneficiary can withdraw after a specified future timestamp. It is a deferred-transfer proposal, not an NFT vesting-claim transfer standard. ERC-5725 illustrates how locked economic rights may be transferable; ERC-7720 illustrates time-gated withdrawal. Neither status proves that a particular project implements the interface.

Worked example: a 12-month cliff and 36-month vest

Assume a contributor receives 12 million tokens. The grant vests linearly over 36 months from the start date, but claims are blocked during a 12-month cliff. Under this specific design, economic accrual is measured from the start even though nothing can be claimed before the cliff. The table shows that economic accrual, not necessarily a contract getter: OpenZeppelin’s VestingWalletCliff returns zero before the cliff and then uses the inherited schedule measured from the original start. The base VestingWallet is linear by default and does not itself add a cliff.

Monthly economic vesting is:

12,000,000 / 36 ≈ 333,333.33 tokens per month

At month 12, the accrued vested amount is:

12,000,000 × 12 / 36 = 4,000,000 tokens

The monthly figure is rounded to two decimal places; use the unrounded fraction for cumulative amounts. Multiplying the displayed 333,333.33 by 12 would give 3,999,999.96, not exactly 4 million. So 4 million tokens can become claimable at the cliff, followed by roughly 333,333 tokens per month until month 36. Actual contracts calculate in their clock units and token base units, with integer rounding; these months are equal-duration illustrative periods, not a specification of calendar-month releases.

This is not the only possible interpretation of “12-month cliff, 36-month vest.” Another contract may define the 36 months as beginning after the cliff, making the total restriction 48 months. Another may release 25% at month 12 and the remaining 75% over 24 months. The phrase is not enough; read the actual schedule.

How token unlocks affect circulating supply

The simplest useful calculation is gross potential float expansion:

unlock size / current circulating supply × 100

Suppose a token has 100 million circulating and 5 million tokens become transferable during a month:

5M / 100M × 100 = 5%

That is a 5% gross unlock relative to the starting float. It is not a prediction that circulating supply will increase by exactly 5%, because the provider may classify some wallets differently, recipients may stake or lock tokens, and the project may burn or otherwise remove supply.

It is also not a price forecast. If only 30% of the unlocked amount is sold, the hypothetical sell quantity is 1.5 million tokens. If the token normally trades $10 million per day, converting tokens to dollars still requires a price assumption and execution schedule before comparing the potential flow with market depth.

A useful analyst therefore asks three separate questions:

1. How much becomes technically available?
2. How much becomes recognized circulating supply?
3. How much is likely to become marginal sell flow?

Only the first may be directly determined by the contract.

Unlocks do not equal sell pressure

A recipient can claim and stake. A foundation can move tokens between custody wallets. A market maker can receive inventory under an agreement that creates two-way liquidity instead of a directional sale. An employee can keep vested tokens untouched.

Conversely, sell pressure can arrive before a headline unlock if economic claims are transferable, hedged through derivatives, or financed against future tokens. This is one reason a simple countdown should not be used as a stand-alone trading signal.

Coinbase has noted the broader tokenomics risk: low circulating float and large future vesting cliffs can make fully diluted valuations look disconnected from the immediately tradable supply, while an unlock can change governance influence and available float. Its institutional report on token inflation instead examines how mining costs, staking incentives and changes in staking ratios affect emission-driven flows; it is not evidence that a particular vesting calendar is wrong. These are reasons to model supply as a range, not to assume every scheduled token hits spot markets at midnight.

How to read a token unlock schedule

Start with the allocation buckets. Team, investors, advisers, ecosystem, treasury, staking incentives, foundation, and community rewards may have different rules.

Then record five fields for each bucket:

Next, map the schedule onto current circulating supply. A 100 million-token unlock means something different when 10 billion tokens already circulate than when only 300 million do.

Finally, compare the potential new float with actual market liquidity. Reported 24-hour volume is a rough context metric, not executable depth. An analyst should not assume that $50 million of reported volume can absorb $50 million of sales without price impact.

Smart-contract risks in vesting

Onchain vesting improves auditability, but code introduces its own questions.

Ownership can matter

OpenZeppelin notes that a VestingWallet is ownable and ownership can be transferred. That means the economic right to future tokens may be transferable even when the token itself has not vested. A project that promises “insiders cannot sell for 24 months” should clarify whether the vesting claim itself can be transferred or economically hedged.

Rebase tokens need special care

If the token balance changes automatically, the amount held by a vesting contract can change without a conventional transfer. OpenZeppelin explicitly warns integrators to account for rebasing behavior so that the intended vested amount is preserved.

Revocable and non-revocable grants differ

Some grants can be stopped when employment ends; others cannot. Coinbase Token Manager documentation distinguishes vesting from lockup: archiving a grant stops future vesting as of an archive date, while previously vested amounts remain potentially payable or claimable subject to their lockup schedule. Pausing instead temporarily blocks payouts and claims. These are product-specific lifecycle controls, not features of every onchain vesting contract; the base OpenZeppelin VestingWallet has no built-in grant-revocation function. Readers should not assume every project grant is immutable.

Timestamps are not calendars

Smart contracts generally work with timestamps or block conditions, while public websites show human dates and time zones. A release shown as “November 1” may execute at a specific UTC timestamp. For large events, record the exact onchain condition rather than relying on a localized calendar card.

Contract upgrades or migrations can change the map

An upgradeable contract, governance vote, emergency migration, token redenomination, or chain move can supersede an old schedule. The archived whitepaper may no longer describe the current mechanism.

The same security principle appears in BTC-Pulse’s token approval guide: identify the actual contract, authority, and current onchain state instead of trusting a ticker or UI label.

Vesting and fully diluted valuation

FDV usually multiplies a token’s price by a supply measure such as maximum or fully diluted supply. It is useful for showing what today’s price would imply if a much larger supply were valued at the same unit price.

But FDV has two major limitations in vesting analysis.

First, it compresses time. A fully diluted supply of ten billion tokens does not tell you whether the last billion unlocks next quarter or ten years from now. FDV is a monetary valuation, not a token quantity.

Second, it does not measure sell propensity. A strategic treasury allocation and an investor cliff can have the same nominal token count but different behavior.

A better dashboard shows at least current circulating market cap, relevant supply definition, the next 12 months of scheduled releases, major cliff dates, and the control rights attached to each bucket.

A practical unlock-risk framework

Use a simple four-part test.

1. Size

Calculate each event as a percentage of current circulating supply. Small absolute numbers can be large for a low-float token.

2. Recipient

Team, investor, foundation, incentive, and market-maker buckets have different motivations. Do not infer intent without evidence, but do not ignore it either.

3. Liquidity

Compare possible sales with order-book depth, spot volume quality, derivatives positioning, and venue concentration. Headline volume alone is insufficient.

4. Flexibility

Ask whether governance or administrators can postpone, accelerate, redirect, burn, stake, or relock supply. A flexible schedule may reduce or increase risk depending on who controls the change.

A high-risk setup is not merely “a lot of tokens unlock.” It is a large release relative to float, concentrated recipients, thin liquidity, and weak transparency around control.

How to verify a vesting schedule yourself

1. Find the project’s latest token allocation or governance documentation.
2. Identify vesting contract addresses or custody wallets when published.
3. Check contract code or verified interfaces for start, duration, cliff, beneficiary, ownership, and revocation behavior.
4. Compare funding transactions with the promised allocation.
5. Check whether governance has changed the schedule after launch.
6. Record the data provider’s definition of circulating, total, and maximum supply.
7. Separate tokens becoming claimable from tokens actually transferred.
8. Separate transfers from deposits to exchanges or sales.
9. Recalculate percentages using the current circulating-supply snapshot.
10. Timestamp the research. Unlock data becomes stale quickly.

If the contract cannot be verified, label the schedule as issuer-reported rather than onchain-confirmed.

Common mistakes

“A cliff means nothing vests before the date”

Not always. Vesting can accrue while claims remain blocked, producing a large first release at the cliff.

“Five percent unlock means five percent price drop”

There is no mechanical one-to-one relationship. Demand, market depth, hedging, recipient behavior, and broader market conditions matter.

“Circulating supply equals unlocked supply”

Providers can exclude foundation, treasury, bridged, staked, or contract-held balances under different methodologies. State whose definition you use.

“A transfer from a vesting wallet is a sale”

It proves a transfer, not the economic reason. Follow the destination before assigning intent.

“Smart-contract vesting cannot be changed”

Some contracts are immutable; others have owners, proxies, migration paths, or external governance. Verify the specific implementation.

“Low float is bullish because fewer tokens are available”

Low float can amplify demand, but a large future supply overhang can also raise dilution and liquidity risk. Both sides belong in the analysis.

Frequently asked questions

What does vesting mean in crypto?

It means an allocation becomes earned, claimable, or transferable according to defined time or milestone rules. The exact legal and technical meaning depends on the project and contract.

What is a token vesting cliff?

A cliff is an initial period before a beneficiary can claim scheduled tokens, or before the first tranche becomes vested, depending on the design. Read the contract to know which applies.

Are unlocked tokens immediately sold?

No. Unlocking gives recipients more freedom to move tokens. It does not prove a sale.

How do token unlocks affect price?

They can increase potential liquid supply. Price impact depends on event size, recipient behavior, market depth, demand, derivatives, and broader conditions. There is no fixed percentage relationship.

Is linear vesting safer than a large cliff?

Linear vesting reduces scheduled jumps, but a beneficiary can accumulate claimable tokens and sell them together. “Safer” depends on liquidity and behavior as well as the schedule.

Can vested tokens still be locked?

Yes. A grant may be vested under one rule while another contractual or onchain restriction still prevents transfer.

BTC-Pulse Take

Token vesting is most useful as a supply-accounting problem, not as a countdown meme. The serious workflow separates entitlement, claimability, circulation, transfer, and sale. It also asks whether the published calendar can be changed and whether the economic claim itself is transferable.

The best information gain usually comes from doing the arithmetic: event size as a percentage of float, the recipient bucket, the release curve, and realistic liquidity. A large cliff deserves attention, but it is evidence of new potential supply—not proof of an immediate dump.

This article is educational and not financial advice. Token schedules, contracts, governance decisions, and supply-provider definitions can change; verify the current primary sources before making a market decision.

Sources

• OpenZeppelin — VestingWallet.sol (official implementation source)

• OpenZeppelin — VestingWalletCliff.sol (official implementation source)

• OpenZeppelin Contracts — VestingWallet (primary technical documentation)

• Ethereum Improvement Proposals — ERC-5725 Transferable Vesting NFT (primary standards document)
• Ethereum ERCs — ERC-7720 Deferred Token Transfer (primary standards document)
• Coinbase Token Manager — Manage token grants (first-party grant documentation)
• Coinbase — Around the Block #13: governance-token risks (secondary/market context)
• Coinbase Institutional — Interpreting Token Inflation (institutional supply-analysis context)