Token research
What Are Token Unlocks?
A token unlock is a point at which previously restricted units become eligible for release or transfer under a schedule. Its relevance depends on how many tokens are affected, who receives them, whether the event changes transferable supply and how much liquidity exists in the markets where the token trades.
Read the release schedule before counting unlocked tokens
Token documents often divide allocations among a team, investors, users, a treasury or ecosystem incentives. Each allocation can have its own vesting mechanism. A cliff is an initial period during which a schedule may produce no releasable amount. Linear vesting makes the vested amount rise over time. A project may distribute vested balances in batches or require recipients to claim them.
Use the project’s latest published schedule, chain and relevant contracts, and record the schedule’s time zone. Different implementations handle vesting after the cliff in different ways. Some make an accumulated amount eligible when the cliff ends. Others structure the first release differently. An example implementation is OpenZeppelin’s vesting wallet and cliff extension. OpenZeppelin’s vesting contracts
Size an unlock against a meaningful denominator
Suppose a fictional project has 1 billion maximum units and 100 million units circulating. Its next release makes 10 million units eligible for transfer. Measured against the maximum, that is 1%. Measured against the current circulating base, it is 10%. Reporting both percentages explains why the same event can look small on one dashboard and large on another.
If all 10 million later meet the provider’s definition of circulating supply and no other supply changes, the circulating estimate could rise to 110 million units. At an unchanged price of $0.50, its calculated market cap would rise from $50 million to $55 million. That example holds price constant to isolate the supply effect. The real price and circulating estimate can both change. How circulating supply affects cap and FDV
Separate the schedule, the release and what recipients do
- Scheduled: a document or contract defines when an allocation becomes eligible.
- Released or claimed: balances move under the mechanism, if a separate action is required.
- Circulating: a data provider judges whether those balances count toward its circulating estimate.
- Traded: units actually change hands in a market where you can identify a trade.
These are different observations. A transfer to a custody address or an exchange deposit address does not by itself show a sale. A release into a grant program may also come with additional restrictions. If the project can amend the schedule through governance or an administrative role, record that possibility and date the source.
Unlocks, emissions, burns and bridges
Unlocking can make existing units accessible. Emissions can introduce units over time under protocol rules. Burns reduce supply under the token’s mechanism. A bridge can lock or account for units on one chain while issuing a representation on another. Counting the backing units and their wrapped counterparts together can distort a supply total. These mechanisms deserve separate notes when you compare circulation across providers. Ethereum on bridge models · CoinGecko supply terminology
How to document the event
Record the token and chain, scheduled date, affected allocation, eligible units, current circulating supply and data sources. Add the actual release or claim transaction when it can be identified. If liquidity is low, include the source pool so readers can separate the size of the release from the depth of trading. Read about pool liquidity.