FINALIZED TRANSACTIONS · DAILY REVIEW

On-chain burns

Follow tokens deliberately burned on Bittensor. Every entry has a finalized transaction behind it.

Minimum 100 tokens per burn

Only individual burns of at least 100 alpha, or 100 TAO for TAO burns, are shown. Totals include qualifying transactions only. Miner emissions and recycling are excluded. Buyback totals show alpha burned; TAO spent is listed separately.

Chain coverage · through block 9,332,665

Reviewed 10/21/2026, 15:19:02 UTC. Blocks 9,325,898–9,332,665, inclusive · Finalized Opentensor archive RPC event scan · runtime 481.

Every block in this archive interval was read for explicit alpha burn, buyback-burn and TAO balance-burn events. Successful transaction events only; automatic miner emissions and recycling excluded. Earlier history has not been backfilled.

History starts 10/20/2026, 16:23:12 UTC. This is a daily reviewed archive, not a live feed or an all-time burn total.

Reset

2 verified burn events

Amounts stay in their own token. Different subnets’ alpha is never added together.

SN8 Vanta

277.894578981 α

2 burn events in this selection

Transaction history

DIRECT ALPHA BURN

SN8 Vanta

126.227912315 α burned
View transaction ↗
Chain evidence
Block
9,332,257
Event
238 · SubtensorModule.AlphaBurned
Account
5EjfvkK…6FV7jc5 ↗
Block hash
0x2529fbfcefca12186b78e3f683a0ecbdf7adab3326336c91982be2acbcf1e505
Execution
Finalized · successful

DIRECT ALPHA BURN

SN8 Vanta

151.666666666 α burned
View transaction ↗
Chain evidence
Block
9,329,053
Event
172 · SubtensorModule.AlphaBurned
Account
5EjfvkK…6FV7jc5 ↗
Block hash
0x52638a236c8c2377097bed7e8dd65bff93427fb666987d2e379d45a241bad7ba
Execution
Finalized · successful

How to read this

A direct alpha burn removes held alpha. A buyback burn uses TAO to acquire alpha and then burns it; the TAO remains in the subnet pool. A voluntary TAO balance burn reduces TAO issuance. None of these guarantees a price increase.

Registration recycling, token transfers, fees, announced buybacks and miner-emission allocations are not counted as executed transaction burns. Cumulative burn-counter changes alone are not sufficient evidence.

Burn and recycling implementation ↗