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.
- 1,615,827.795 BNB
- Quarterly burn amount
- 2026-07-15
- Announcement date
Historical quantity, not a live quote or the entire change between supply snapshots.
On this page
| Record | BNB | Source timestamp |
|---|---|---|
| 35th announcement: remaining supply | 134,786,916.53 | 15 April 2026, 11:55 UTC |
| 36th announcement: remaining supply | 133,166,127.91 | 15 July 2026, 10:35 UTC |
| 36th announcement: burn amount | 1,615,827.795 | The stated quarterly event |
These three figures produce a residual. They do not, on their own, tell us what caused it. This is a historical reconciliation case; the editorial review date does not refresh the underlying supply snapshot.
Two subtractions, two different meanings
The 35th announcement supplies the April figure, while the 36th announcement supplies July's remaining quantity and event amount. Subtracting the displayed supply snapshots gives 1,620,788.62 BNB. Subtracting the quarterly event from that change leaves 4,960.825 BNB. This is arithmetic on displayed values, whose final precision is limited by the inputs.
The first difference is the net reduction between two publication snapshots. The second is the part not explained by the listed July event alone. It is not an independently verified BEP-95 amount, nor does it automatically demonstrate an error in either announcement.
The snapshots are months apart, not adjacent states around one transaction. Attributing the residual requires matching records for the interval, consistent scope and a check for other adjustments. Knowing a possible mechanism is not enough to assign it an exact amount.
A reverse calculation makes the same point. Adding July's event back to July's remaining supply produces 134,781,955.705 BNB. That is a derived reference number, not a verified pre-transaction state at a particular block. It still differs from the April snapshot. Reversing the arithmetic has moved the residual, not explained it.
In a spreadsheet, label April's figure “previous announcement snapshot”, rather than “supply immediately before this burn”. The supply ledger guide separates those timestamps so a convenient column name does not quietly become a false factual claim.
Event quantity, lifetime counter and dollar estimate
The July announcement also gives an approximate burn-time valuation of $931,702,464. That is a historical estimate, not cash paid to holders, a rebate or the cost of buying the same quantity now. Dividing it by the token amount gives an implied ratio, not proof of a market execution at that price.
The same source discusses a cumulative fee-burn counter. A lifetime counter cannot be added to one quarterly event and relabelled as that quarter's total. You need the fee mechanism's increment over the relevant interval. Conversely, independent flows really can be added when their asset, period and scope match. The two-mechanism comparison sets out those conditions.
Percentages need a denominator too. Dividing this event by April's snapshot answers a different question from dividing it by an immediate pre-burn supply figure. A headline percentage without its denominator is not suitable for comparison with another report's percentage.
I keep token quantity ahead of dollar valuation in an event record. Otherwise, a chart can suggest that the burn grew when only the chosen token price increased. Preserve the announcement's “remaining total supply” label as well: replacing it with “circulating supply” would introduce a different accounting question.
The transaction link supports one part of the record
The announcement provides an execution link and identifies BSC as the network for this quarterly action. Start from that original link when checking the network, status, asset and destination. Do not select an unrelated search result merely because its label includes “burn”.
This article verifies the announcement's stated figures and their arithmetic. It does not claim independent-node reconstruction, complete interval fee statistics or an audit of the assets' funding origin. Those would be additional investigations.
A successful transfer is not the same as a full supply reconciliation. The destination's balance may include earlier events and unrelated transfers, while a transaction's network fee is a separate quantity from its transferred asset. The burn-address evidence guide explains why neither should be substituted for this event amount.
The useful result is narrow: the displayed snapshots and event quantity leave a 4,960.825 BNB residual that is not attributed here. Preserve it as an open item. A later source may explain it, but an explanation should be added with its own scope and date rather than silently inserted into this historical record.