Token supply mismatch: build a reconciliation ledger

An announcement, a block explorer and a market-data page show three different supply figures. Before choosing which one to trust, check whether they describe the same asset, at the same time, under the same definition. A disagreement becomes a useful question only after those conditions are clear.

A ticker is not an asset identifier

For a contract token, record both its network and its contract address. A familiar name or logo is not enough: names can be reused, and the same address format can appear on different networks. For a native coin, record the network and its native-asset identity instead of inventing a token contract to make the spreadsheet look consistent.

When a token appears on several chains, establish the relationship between those versions before adding anything. In a reserve-backed wrapping model, a representation and the underlying locked assets may describe the same economic claim. Adding both as newly created supply would count that claim twice. A migration, an independently issued version and an unrelated token with the same name require different treatment.

Do not assume that every product described as “multichain” has a verified one-to-one reserve. Look for the actual documentation of issuance, custody and redemption. If that relationship remains unclear, keep separate ledgers. I prefer two explicitly incomplete records to one combined number whose meaning cannot be explained.

This distinction also helps keep a small practical problem from becoming an unnecessary research project. If a wallet holds WBNB but cannot pay a network fee, begin with native and wrapped balances. That is a question about what a balance can do, not necessarily about the global supply of BNB. Reading public supply information does not require connecting a wallet or entering a recovery phrase.

Preserve the label before interpreting the number

Four fields that should not share one spreadsheet column

Field	Question it can address	Inference to avoid
Total supply	How much the source counts as existing	All of it is immediately for sale
Circulating supply	How much the source includes in public circulation	Every transferable balance is included
Maximum supply	The source's maximum-supply definition	Everything has already been issued
Burned	A burn amount within a stated scope	A lifetime counter is this quarter's flow

Circulating supply involves classification as well as arithmetic. The CoinMarketCap methodology and CoinGecko supply methodology describe their approaches. Excluded wallets, supporting disclosures and the timing of a revision can differ. Two services need not be counting exactly the same public float.

The useful part of a methodology is the path to reconstruction. Which balances were excluded? At what time were they read? Did an address change category? A statement such as “total minus non-circulating wallets” is not enough to reproduce the result without those inputs. If they are unavailable, describe the number as a provider figure, not as your independently verified calculation.

Unlocking and issuance deserve separate columns. An already-issued allocation can become transferable without increasing total supply. A provider may then include it in circulation, depending on its method. Conversely, transferability does not demonstrate that an allocation has been sold. A transfer condition, a provider classification and a market transaction are different observations.

The time you opened a page is not its data time

Keep an access timestamp for your research record and a data timestamp for your calculation. An announcement opened on Friday may contain Wednesday's snapshot. Two dashboards opened together may use different upstream refresh schedules. “Viewed at the same time” does not make the figures contemporaneous.

Preserve the stated timezone. If a source gives only a date, do not silently assign midnight to it. A block height can provide a more precise state reference, but only when it actually belongs to the figure being quoted. Without comparable historical readings, the result may support a broad comparison rather than an exact attribution.

Flows need a start and an end. A quarterly event amount cannot be treated as interchangeable with a counter accumulated since a mechanism began. Subtracting two cumulative readings can give a period increment if their scope remained unchanged. If the service revised its coverage between readings, that revision must be accounted for too.

Preserve source precision before rounding. An abbreviated value such as “about one million” cannot support a claim about a difference of a few hundred units. Check imported spreadsheet values as well: scientific notation, decimal separators and automatic text conversion can create errors that look like supply discrepancies. Never repair them by deleting punctuation until the formula happens to work.

Build a movement table, then leave the residual visible

A comparable total-supply reconciliation starts with opening supply, adds confirmed issuance, subtracts confirmed burns and includes documented methodology adjustments. An ordinary transfer is not issuance, and a payment from a treasury is not automatically a burn.

1,000,000 opening + 20,000 issued − 5,000 burned = 1,015,000 closing

If the closing source instead reports 1,014,000, the unexplained difference is 1,000. Do not insert “other burns: 1,000” merely to balance the table. The residual could reflect a missing event, a timestamp mismatch, a unit error or a methodology revision. The equation identifies missing explanation; it does not identify the explanation itself.

Circulation needs its own movement table. Reclassifying 30,000 already-issued units from excluded to circulating can change public float while leaving total issuance unchanged. Mixing this reclassification into the issuance column would tell the wrong story even if the final arithmetic happened to balance.

Associate each movement with an event or source and state whether it is already included in another total. Independent, non-overlapping burn flows for the same interval can be added. A component already contained in a published total cannot. The Auto-Burn and BEP-95 comparison applies this distinction to a specific case.

Keep “not comparable yet” separate from “comparable but unreconciled”. The first requires better identity, scope or time information; the second requires missing movements. That distinction stops you from spending hours searching transactions when the original mistake was comparing different assets.

Execution, destination and supply state are separate evidence

A successful transaction supports a claim about execution on a particular network. It does not by itself establish a change in every supply field. A transfer to an address treated as inaccessible may remain visible in a contract balance while being excluded from an economic supply measure.

The ERC-20 specification includes a supply-reading interface. The interface name does not establish that a particular transfer invoked burn logic. Actual implementation and comparable before-and-after state matter. Native coins must instead be assessed using the relevant network's rules; a wrapped-token contract is not a substitute for the entire native asset's supply.

Read explorer fields carefully. “Value”, token-transfer records and event logs may describe different assets or different layers of the same operation. Network execution fees should not be appended to a token burn amount without a separate, applicable mechanism. Our burn-address evidence guide explains what each layer can support.

A real example can remain partly unresolved

The April and July 2026 BNB quarterly announcements provide two dated remaining-supply snapshots. They are not the immediate states on either side of one transaction. Their difference therefore describes the change between announcement snapshots, rather than automatically describing only July's quarterly burn.

35th announcement · remaining total supply
2026-04-15 11:55 UTC

134,786,916.53 BNB

36th announcement · remaining total supply
2026-07-15 10:35 UTC

133,166,127.91 BNB

36th announcement · event burn

1,615,827.795 BNB

1. Snapshot decrease: 134,786,916.53 − 133,166,127.91 = 1,620,788.62 BNB.
2. Less the 36th burn: 1,620,788.62 − 1,615,827.795 = 4,960.825 BNB.

Sources rechecked on 13 September 2026. This arithmetic uses the published decimals, not an independent reconstruction at chain-level precision. The residual has no verified attribution here. Calling it BEP-95 would require records covering the same interval. Do not subtract the 35th burn again: it precedes the opening snapshot. See the 36th-burn case for the remaining evidence limits.

Several news pages repeating one announcement do not provide several independent proofs. A more useful combination is an original explanation, execution evidence and a supply methodology, each answering a different question. Project statements about hoped-for economic benefits should also remain distinct from verifiable descriptions of protocol behavior.

Make the record usable by the next reader

Save the asset identity, original field label, unrounded value, data time, source, comparability status and unresolved difference. If later evidence changes a figure, add a dated correction instead of silently replacing the old observation. When an old page has changed but no historical copy is available, say that the revision time is unknown.

Keep your own estimates visibly separate from published figures and from independently reconstructed records. All three can be useful, but they should not share one blanket “verified” label. The question is whether another reader can follow the same evidence as far as your conclusion goes.

A finished record may say “reconciled”, “partly explained” or “not comparable with available information”. None of those requires a price forecast. Supply accounting addresses quantities; price effects after a burn depend on additional conditions. Leaving that boundary intact makes the ledger useful even when the market behaves differently from expectations.