GGlossary · 1 min read

What is an unlock cliff?

An unlock cliff releases a whole tranche of locked or vested tokens on one date, not gradually. How cliffs work and how to see the next one coming.

318 words · about 1 minute·Article updated 20 August 2026
Definition

An unlock cliff is a date on which a batch of previously locked or vested tokens becomes available all at once, rather than releasing gradually. Before the cliff nothing releases; at the timestamp the whole tranche is claimable. The exact date is on-chain from creation.

The shape matters more than the size. Say a team locks a tranche with a twelve-month cliff and no linear release after it: for a year the on-chain balance does not move at all, and then the entire tranche is withdrawable in a single block. A schedule with a short cliff followed by monthly releases produces many small events instead of one large one. Same total, very different supply picture on the day.

A cliff is a date, not a prediction. Nothing forces the holder to sell when it passes, and nothing stops them.

A lock guarantees exactly one thing: the pool cannot be withdrawn before the release date. Not the price, not the team, not the token. A locked pool can still fall.
Where you'll see it on Locksley

Token pages show a countdown to the next release timestamp, read from the lock or vesting contract rather than from an announcement. Unlocks this week lists the pending releases due in the next seven days across the chain.

For what actually happens at the timestamp, read what happens when a lock expires; for how to think about the window beforehand, extend, exit, or hold. The underlying mechanism is the liquidity lock.

Frequently asked questions

Is an unlock cliff the same as a vesting schedule?

A cliff is one component of a schedule, not the whole thing. The schedule describes everything: how much, to whom, over what period. The cliff is the date before which nothing at all is released. A schedule can have a cliff then linear releases, a cliff and nothing else, or no cliff and steady release from day one.

FiguresEvery number on this page is frozen at the date printed beside it and refreshed when the page is rebuilt — not live. The sentences reason about the figures, so a value that changed underneath them would make the prose wrong. Live values live on Explore and the pages it links out to. Methodology →
CorrectionsFound something wrong? Send the page and what you computed instead through the contact page. Every correction is logged publicly.
ReusePublished under CC BY 4.0. Quote it, translate it, fork it — cite the page and the date.
Who wrote thisWritten and maintained by the Locksley editorial team. Locksley is built by TrustSwap, which also owns Team Finance — the tool linked above.