Node Sale Allocation
A node sale allocation is the slice of token supply reserved for buyers of a node licence or node hardware.
TradFi parallel: Closer to selling franchise licences than to a share placement: the buyer pays for the right to operate, and the operating rewards accrue afterwards.
Key Takeaways
- 01Start with the definition: A node sale allocation is the slice of token supply reserved for buyers of a node licence or node hardware.
- 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 node sale allocation is the slice of token supply reserved for buyers of a node licence or node hardware.
The label alone does not establish a token's current supply impact. To evaluate node sale allocation, 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.
Frequently Asked Questions
How is a node sale different from a public sale or launchpad round?
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 node buyers receive their tokens at TGE?
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 should I model a node allocation in a supply forecast?
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 projects run node sales instead of raising conventionally?
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.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