Token supply mismatch: build a reconciliation ledger
Separate timestamps, token identity and supply definitions before reconciling explorer, announcement and market-data figures.
BNB burn archive
Completed quarterly events, recorded from primary announcements. Two reviewed examples, not a complete history or live feed.
| Event | Announced | BNB burned | Source |
|---|---|---|---|
| Burn 36 | 2026-07-15 | 1,615,827.795 | Original announcement ↗ |
| Burn 35 | 2026-04-15 | 1,569,307.34 | Original announcement ↗ |
The 36th BNB burn: reconcile the supply snapshots
A dated arithmetic case: compare two supply snapshots without treating their residual as a verified fee-burn total.
Auto-Burn and BEP-95: when burn totals can be added
Independent burn flows can be added for the same period. Cumulative counters and totals that already include a component cannot.
What a burn address proves, and what it does not
Distinguish a successful transfer, an inaccessible balance and a supply-state change before describing tokens as burned.
Token buybacks and burns need different evidence
Trace funding, completed purchases, token destinations and supply changes without confusing one action with another.
Why a token price can fall after a burn
A supply reduction does not fix demand, liquidity or valuation. Test the assumptions behind a claimed price effect.