Halving

It normally fires at a block height rather than on a date, and on Bittensor at a level of cumulative issuance, so the emission curve steps down rather than tapering.

TradFi parallel: Closest to a dividend policy written into the charter rather than voted each year: the payout rate is cut on a published trigger, nobody decides it at the time, and the whole market knows it is coming years ahead.

Key Takeaways

01
Start with the definition: It normally fires at a block height rather than on a date, and on Bittensor at a level of cumulative issuance, so the emission curve steps down rather than tapering.
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

It normally fires at a block height rather than on a date, and on Bittensor at a level of cumulative issuance, so the emission curve steps down rather than tapering.

The label alone does not establish a token's current supply impact. To evaluate halving, 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.