KPI-Gated Unlock
A release conditioned on a published, measurable performance threshold rather than a calendar date.
TradFi parallel: An earnout in an acquisition, or a performance-vesting equity grant. The shares are allocated and the recipient is named, but nothing is delivered until a stated metric clears a bar, so the delivery schedule follows the business rather than the calendar.
Key Takeaways
- 01Start with the definition: A release conditioned on a published, measurable performance threshold rather than a calendar date.
- 02Read the governing documentation before treating a label as a supply conclusion
- 03Separate scheduled entitlement, contractual transferability, and actual circulating supply
- 04Use dated on-chain or canonical data for any amount, percentage, or event date
- 05A buyback, unlock, burn, or reward label does not by itself establish the net supply effect
- 06Remove or qualify any project-specific conclusion that cannot be reproduced from a primary source
How It Works
A release conditioned on a published, measurable performance threshold rather than a calendar date.
The label alone does not establish a token's current supply impact. To evaluate kpi-gated unlock, 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
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 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.
Frequently Asked Questions
How is a KPI-gated unlock different from TBD locked supply?
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.
Does a KPI gate reduce 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.
Who verifies that a KPI has been met?
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 track a KPI-gated tranche?
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
tbd locked supplytreasury vestingtoken generation eventvesting schedulelow float high fdvwhitepaper schedule
Track on Tokenomist
Supply-side analysis for educational purposes. Not financial advice. Verify assumption and precision labels on the relevant token page.
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