Build and Backtest Tokenomist API
Tokenomist

Unlock Price Impact

Unlock price impact is the measured price behaviour around a token unlock across three windows: the drift before the date, the reaction on the day, and the path after it.
TradFi parallel: Closest to an IPO lockup expiration, where the date is public long in advance. The parallel is loose, since the equity work on lockups is usually read as small effects clustered around the expiry rather than a repricing spread across the preceding weeks.

Key Takeaways

  • 01
    Start with the definition: Unlock price impact is the measured price behaviour around a token unlock across three windows: the drift before the date, the reaction on the day, and the path after it.
  • 02
    Read the governing documentation before treating a label as a supply conclusion
  • 03
    Separate scheduled entitlement, contractual transferability, and actual circulating supply
  • 04
    Use dated on-chain or canonical data for any amount, percentage, or event date
  • 05
    A buyback, unlock, burn, or reward label does not by itself establish the net supply effect
  • 06
    Remove or qualify any project-specific conclusion that cannot be reproduced from a primary source

How It Works

Unlock price impact is the measured price behaviour around a token unlock across three windows: the drift before the date, the reaction on the day, and the path after it.
The label alone does not establish a token's current supply impact. To evaluate unlock price impact, read the governing token documentation and contract rules, distinguish scheduled entitlement from tokens that are actually transferable or circulating, and use dated on-chain data for any quantity. Do not infer a burn, price effect, holder behavior, or release amount from the label alone.
When a claim depends on a figure, date, allocation, fee route, or prior market event, retain it only when the underlying primary document, governance record, contract state, or reproducible data snapshot is available. Otherwise state the mechanism generally and leave the project-specific conclusion out.

Real World Examples

Scenario 1: verify before concluding
Use the project's published rules, the relevant contract or governance record, and a dated supply snapshot. Keep only conclusions that those records directly support.
Scenario 2: verify before concluding
View →
Use the project's published rules, the relevant contract or governance record, and a dated supply snapshot. Keep only conclusions that those records directly support.
Scenario 3: verify before concluding
View →
Use the project's published rules, the relevant contract or governance record, and a dated supply snapshot. Keep only conclusions that those records directly support.
Scenario 4: verify before concluding
View →
Use the project's published rules, the relevant contract or governance record, and a dated supply snapshot. Keep only conclusions that those records directly support.
Scenario 5: verify before concluding
Use the project's published rules, the relevant contract or governance record, and a dated supply snapshot. Keep only conclusions that those records directly support.

Frequently Asked Questions

If the drop happens before the date, is there anything left to trade on unlock day?
Check the governing documentation, contract state, and dated on-chain or canonical data. The answer depends on the project's specific rules and current supply state, so do not infer it from the label alone.
Why do some tokens rise through an unlock?
Check the governing documentation, contract state, and dated on-chain or canonical data. The answer depends on the project's specific rules and current supply state, so do not infer it from the label alone.
How do I measure unlock price impact properly?
Check the governing documentation, contract state, and dated on-chain or canonical data. The answer depends on the project's specific rules and current supply state, so do not infer it from the label alone.
Do insider unlocks hit harder than community unlocks?
Check the governing documentation, contract state, and dated on-chain or canonical data. The answer depends on the project's specific rules and current supply state, so do not infer it from the label alone.
How does this differ from supply pressure?
Check the governing documentation, contract state, and dated on-chain or canonical data. The answer depends on the project's specific rules and current supply state, so do not infer it from the label alone.

Related Terms

Track on Tokenomist

Supply-side analysis for educational purposes. Not financial advice. Verify assumption and precision labels on the relevant token page.
Tokenomist
Tokenomist.ai provides a complete solution for supply-side tokenomics data. Analyze future token emissions, track vesting schedules, and compare standardized tokenomics and allocation across projects to gain actionable insights