Token supply mismatch: build a reconciliation ledger
Separate timestamps, token identity and supply definitions before reconciling explorer, announcement and market-data figures.
BNB utility & rule watchReview dates: see each page
How much BNB is burned each quarter? The 35th and 36th quarterly burn amounts and announcement dates, taken from the official announcements. Not a complete history or a 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 ↗ |
Separate timestamps, token identity and supply definitions before reconciling explorer, announcement and market-data figures.
A dated arithmetic case: compare two supply snapshots without treating their residual as a verified fee-burn total.
Independent burn flows can be added for the same period. Cumulative counters and totals that already include a component cannot.
Distinguish a successful transfer, an inaccessible balance and a supply-state change before describing tokens as burned.
Trace funding, completed purchases, token destinations and supply changes without confusing one action with another.
A supply reduction does not fix demand, liquidity or valuation. Test the assumptions behind a claimed price effect.
BNB shows up on opBNB and in a legacy ERC-20 contract on Ethereum. Adding those balances to the BSC figure double counts. Read the bridge contract, the official swap notes and a node query you can repeat.
Over 25 million BNB sits in BSC validator staking contracts, and the old TokenHub cross-chain contract holds a similar amount. Both can be withdrawn, so neither comes off total supply. Contract evidence, node queries and the size of the error if you subtract them.