Build and Backtest Tokenomist API
Tokenomist

Claim Restraint

Claim restraint is a beneficiary repeatedly claiming materially less than its vesting schedule entitles it to, leaving the balance sitting unclaimed in the vesting contract.
TradFi parallel: Like an insider whose options have vested but who keeps declining to exercise them. The right is fully earned and the shares are not issued, so the dilution exists on paper and not in the share count.

Key Takeaways

  • 01
    Start with the definition: Claim restraint is a beneficiary repeatedly claiming materially less than its vesting schedule entitles it to, leaving the balance sitting unclaimed in the vesting contract.
  • 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

Claim restraint is a beneficiary repeatedly claiming materially less than its vesting schedule entitles it to, leaving the balance sitting unclaimed in the vesting contract.
The label alone does not establish a token's current supply impact. To evaluate claim restraint, 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.
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
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

Does an unclaimed allocation expire?
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 would a team claim less than it is owed?
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.
Is claim restraint bullish?
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.
Where do I see the gap between entitlement and claim?
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