Points Program
A points program awards non-transferable units for specified user activity before a token exists.
TradFi parallel: Like airline miles issued before the airline has published a redemption chart: the balance accrues while the issuer keeps the right to decide what it converts into, and how many more it will print in the meantime.
Key Takeaways
- 01Start with the definition: A points program awards non-transferable units for specified user activity before a token exists.
- 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 points program awards non-transferable units for specified user activity before a token exists.
The label alone does not establish a token's current supply impact. To evaluate points program, 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
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
Are points worth anything before the token exists?
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 is a points program different from an airdrop?
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.
Can the issuer change the rules mid-program?
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.
What does a points-led distribution do to the float at launch?
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.