How Token Unlocks Work

How Token Unlocks Work

Published
AuthorDevansh

A token unlock is a date when locked tokens become free to move. When a project launches, most of its supply is not circulating. Team, investor, foundation, and community allocations sit in vesting contracts and release on a published schedule. On unlock day, those tokens can be transferred, sold, staked, or used - and the circulating supply grows by that amount. This post explains how the schedules work, what this week's actual unlocks are, and why a node operator should care about unlock week even though it is not a price event.

If staking mechanics are new to you, start with our staking explained guide. Unlocks sit on top of the same idea: who holds the tokens, when they can move them, and what changes for the network when they do. This post is about the schedule, not about whether any token is worth buying. That is not a question infrastructure can answer.

What a token unlock is

At a token generation event, a project mints its total supply and splits it into allocations: team, early investors, foundation or treasury, ecosystem rewards, and public sale. Almost none of the team and investor allocations are free on day one. They are locked in a vesting contract with a schedule the project publishes in its tokenomics. The schedule exists for a simple reason: if insiders could sell everything at launch, there would be no reason to trust that they will still be building in a year. Locking aligns their timing with the project's timing.

The schedule names three things: who gets the tokens, how many, and when. The "who" is usually a bucket like team, private investors, or foundation. The "how many" is a token count and often a share of circulating supply, which matters more than the raw count - 100 million tokens is a small event for a large-cap token and a huge one for a small one. The "when" is the unlock date, and it is the only part that is truly fixed. Dollar values are not fixed: they move with the token price, so the same unlock can be worth very different amounts on different days. Always read the token count and the share of supply first, and the dollar figure second.

Cliff vs linear vesting

There are two basic shapes. A cliff means nothing unlocks for a set period, then a chunk unlocks all at once. A 12-month cliff is the most common: a team's allocation is fully locked for a year after launch, then a portion - often a third - becomes free on the anniversary. After the cliff, the rest usually releases on a linear schedule. Linear vesting means tokens release steadily, a little every day or every block, over months or years. A linear release spreads the supply increase out so no single day carries it all.

Cliffs are the dates that matter most, because a whole tranche lands on one day. This week's biggest example is a first cliff: Allora's core contributors and early backers get their first tokens on Wednesday, November 11, about 160 million ALLO, worth roughly $24.1 million at the price when the schedule was reported. Their allocation was locked for 12 months after launch, and a third of it frees now. Linear releases are quieter but never stop - Solana, for example, releases staking-related supply on a regular monthly rhythm, and Aptos releases a few million APT to its community pool and foundation on a monthly cycle too. Both shapes are normal. The mistake is treating a cliff like a linear release, or assuming a linear release has a single big day.

This week's unlocks, November 9 to 15

The week opens with ADI Chain on Monday, November 9: a release of about $56.18 million, equal to 7.18 percent of its market capitalisation, according to CryptoRank data reported on November 2. Wednesday, November 11 is the busiest day. Allora's first cliff lands at 13:00 UTC, about 160 million ALLO, roughly $24.1 million. Pump.fun releases about 6.9 billion PUMP, roughly $25 to $26 million, its monthly team and investor tranche. Aptos releases about 4.5 million APT, roughly $2.7 million, to its community pool and foundation. Solana's monthly staking unlock, about 397,000 SOL, roughly $42 million at one tracker's count, also falls on November 11.

Saturday, November 14 carries the week's most argued-over event: Pieverse. One tracker puts the release at about $125.61 million, 31.44 percent of supply. Another puts the same event at about $24.3 million. The gap comes from different counting methods and different supply definitions, and it is a useful warning: never quote one tracker's dollar figure as a fact without checking a second source. Sunday, November 15 brings Starknet's monthly release for investors and early contributors, about 127 million STRK, roughly $5 million, plus smaller Sei and Arbitrum tranches. Look further out and the month's biggest event is Monad on November 24: about 16.6 billion MON, roughly $324 million, as team and investor allocations unlock after their cliff, one year after mainnet.

Why trackers disagree about the same week

If you compare two unlock calendars for this week you will get different totals, and both can be honest. One summary puts the week's scheduled releases at about $605 million. Another counts only about $56 million in one-off tranches. The difference is what they count: one includes every linear drip and recurring monthly release, the other counts only single-day cliff tranches. Some trackers count a whole allocation when its cliff date arrives, even though only a third of it vests that day - that is how Allora's $24 million first cliff shows up as $73 million in some summaries. And prices move, so a dollar figure stamped on Monday is stale by Wednesday. The fix is simple: read the token count, the share of circulating supply, and the holder bucket, and treat dollar totals as a rough sense of scale, not a precise number. When two trackers disagree by a factor of five, say so, and use the smaller, better-sourced figure.

Why node operators care: traffic, not price

An unlock is not a price prediction, and this post makes none. What an unlock reliably does is move traffic. On unlock day, holders check balances, move tokens to exchanges, and query explorers and wallets far more than usual. RPC endpoints see a spike in balance and transfer queries. Support channels see questions about vesting and claiming. For a team running infrastructure for a chain with an unlock, the week is an operations event: watch RPC latency, watch disk and peer counts, and make sure your status page and support answers are ready before the date, not after. Our week in review puts this week's unlocks next to the launch calendar, so you can plan both in one place.

An unlock-week checklist for operators

First, list the unlock dates that touch chains you run infrastructure for, and note the holder bucket - a team unlock and a community unlock create different traffic. Second, check RPC capacity and failover a day early, and confirm your fallback endpoint is synced. Third, pre-write the support answer: when tokens unlock, how holders claim or move them, and where the official schedule lives. Fourth, freeze non-essential changes on unlock day itself - do not combine an unlock with a client upgrade. Fifth, after the date, check that your node stayed synced through the spike and note what actually happened, so next unlock week starts from evidence instead of guesses. Five small steps, and the week becomes routine instead of a scramble.

What unlocks do not tell you

An unlock tells you supply is becoming movable. It does not tell you holders will sell, it does not tell you the price direction, and it does not tell you anything about the project itself. A large unlock for a healthy project with real usage is a different event from the same-sized unlock for a project with no users, and the schedule alone cannot tell them apart. Never trade on an unlock date, never promise anyone an outcome from one, and never present a tracker's dollar figure as a forecast. The honest use of unlock data is operational: know the dates, know the size relative to supply, prepare the infrastructure, and let the market do whatever it does.

Unlock schedules are public, dated, and checkable, which makes them one of the few reliable planning tools in crypto. Use them that way. If you run infrastructure for a chain with an unlock coming up and want the RPC, monitoring, and support side ready before the date, book a free infra audit with DevOpsBY. We run nodes, RPC, and validator infrastructure for Web3 teams, and unlock week is exactly the kind of date we plan around.

Disclaimer: This post is educational only, not financial advice. Figures are listing or project data as of 2026-11-09 and may change - always confirm version numbers, requirements, and dates in the official docs before acting on them.

Related Articles

DevOps & Infrastructure Services

Need hands-on help? We build and manage the infrastructure behind the concepts covered in this article.

DevOpsBy Assistant

How can we help?

Select a topic to get started: