INDEPENDENT THINKING. ON EVERY BLOCK.RESEARCH / REVIEWS / GUIDES

Cliff vs. linear token vesting: how many tokens unlock this month?

Read a token vesting schedule, distinguish a catch-up cliff from a delayed start, and calculate how many newly vested tokens become available in a period.

A bronze token emerges from a melting ice cube.

A project says its team allocation has a three-month cliff. How many tokens can the team claim when those three months end? You need one more sentence from the agreement: does vesting accumulate during the wait, or does it start afterward? Those arrangements put different numbers on the same date. Monad’s November 2026 investor cliff shows how twelve months of vesting can appear as a single entry on an unlock calendar.

Put two schedules side by side

Take a grant of 120,000 tokens. In Schedule A it vests in 12 equal monthly steps, counting from the grant date. A three-month cliff prevents claims until the third monthly anniversary. In Schedule B the same 12 monthly steps start after a three-month wait, with the first step payable at the end of month four. These are illustrative terms.

Month-endA: total vested and claimable if unclaimedB: total vested and claimable if unclaimed
Month 200
Month 330,0000
Month 440,00010,000
Month 12120,00090,000

Schedule B finishes at month 15. If a token calendar says only “three-month cliff, 12-month vesting,” check the actual start date, end date and release frequency before building your own table. Some contracts accrue continuously. Others move in steps, as this example does. OpenZeppelin’s vesting wallet documentation describes a stepped implementation in which the cliff permits catch-up at its boundary.

Calculate the unlock during a particular month

Subtract the cumulative vested total at the start of the period from the total at the end. In Schedule A, month four adds 10,000 tokens, even though the cumulative figure reaches 40,000. If the beneficiary claimed nothing at month three, a 40,000-token claim at month four could include the earlier 30,000. Counting the whole claim as a fresh month-four unlock would overstate the schedule.

The denominator matters as well. If a project has 1,000,000 tokens circulating before an event, a 30,000-token unlock equals 3% of that figure. It equals 25% of the 120,000-token grant. Write down which supply you used whenever you share a percentage.

Monad’s November 2026 cliff in numbers

Monad’s investor allocation puts a real number on the difference between a cliff and a monthly installment. Its token sale disclosure assigns about 19.7 billion MON to investors over four years, with a one-year cliff and monthly unlocks of 1/48 of the allocation thereafter. One ordinary monthly slice works out to about 410.4 million MON.

When we checked on November 23, 2026, DefiLlama’s Monad calendar listed 4.925 billion MON for investors on November 24. That is twelve monthly slices at once: 19.7 billion × 12 ÷ 48. The calendar lists team and treasury tokens separately. Adding those rows would answer a different question about the total scheduled across all three groups.

That 4.925 billion is the calendar’s estimate of what investors could access at the cliff. To answer how many tokens actually moved, you would need records from the relevant wallets after November 24. To say how many were sold, you would also need evidence of trades.

What needs separate evidence

A schedule gives a beneficiary the ability to claim or transfer according to its terms. A sale requires separate evidence. Check who the allocation belongs to, whether the published dates are estimates, and whether the reported figure describes availability, an actual claim or a transfer. Even a transfer to another address leaves the price and purpose uncertain.

Our market cap and FDV example shows how changing the supply assumption alters the valuation.