ReserveBeat monitors public stablecoin figures — issuer-published attestation reports and independently measured on-chain supply — with the methodology and its limits rendered on every page. Nothing here is a solvency claim about any issuer.

← All posts

How ReserveBeat measures stablecoin reserves: a methodology deep-dive

ReserveBeat measures stablecoin reserves from two primary sources: on-chain token supply read from Ethereum contracts through a byte-for-byte RPC quorum with storage proofs where possible, and issuer-published attestation reports captured and hash-anchored before parsing. Coverage ratios divide only figures the same document states at the same as-of date, and absence renders as absence.

By Aaron Cohen

Every figure on the coverage board was measured under one reviewed methodology document, and this post walks through how that measurement actually works — including what it refuses to do. Nothing here is a solvency claim about any issuer: tracked tokens are subjects of public data, and no tracked issuer is a customer of ours.

The instinct in this category is breadth: more tokens, more chains, more tiles. But a dashboard is only as trustworthy as its least-supported figure, and breadth is usually purchased by relaxing sourcing standards one tile at a time. ReserveBeat's bias runs the other way — fewer figures, each carrying its source tier, its as-of date, and its stated limits, with absence rendered as absence. A reader who knows exactly how a number was measured can decide what it is worth; a reader facing a wall of unsourced numbers can only decide whether to trust the wall.

On-chain supply: proven where possible, labeled where not

Supply is snapshotted at finalized Ethereum blocks through a quorum of independent RPC providers that must agree byte-for-byte. Each figure carries a provenance tier. The stronger tier, STORAGE-PROVEN, means the total-supply storage slot was read via eth_getProof and the proof verified locally against the block's state root. For example, the board's USDC supply reading of 50,628,892,410.424247 at block 25,528,320 (snapshotted 2026-07-14) is storage-proven — see the source-tier glossary entry for the weaker QUORUM ETH-CALL tier.

If quorum legs diverge, the snapshot blocks: the divergent responses land as evidence, an incident opens, and nothing publishes from a disputed read.

Averaging divergent reads would publish a number that no provider actually returned. If independent providers disagree about a finalized block, the disagreement is the finding — a provider is wrong, or an assumption is — and the honest output is an incident, not a midpoint. A blocked snapshot costs one data point. A smoothed-over divergence costs the reason to believe every other data point.

Attestation parsing: capture first, refuse on drift

Issuer reserve reports are captured and hash-anchored before parsing. Parsing runs against pinned per-issuer templates that refuse on layout drift: a document that does not cross-foot, or whose section anchors moved, lands nothing beyond the captured source. Line labels are stored verbatim — normalization never discards what the issuer actually said. Issuer reissues and parser upgrades are both handled by restatement: a new parse supersedes the old row, and the old row stays independently verifiable.

Coverage ratios: the honesty core

A coverage ratio only ever divides two figures from the same issuer attestation at the same as-of date. Circle's May 2026 USDC report states 75,961,621,872 dollars of total reserve assets and 75,885,403,148 USDC in circulation, both as of 2026-05-29 — a ratio of 1.001004. On-chain measurements never enter a ratio.

Reports whose stated scope is a consolidated group — one redemption value across every token an issuer issues — yield no per-token ratio unless the document itself itemizes the token. That is why the board's USDT page shows a consolidated figure and its stated scope instead of a ratio.

The evidence chain behind every figure

Every artifact behind the board — quorum logs, storage proofs, captured PDFs, parsed reports, the methodology document itself, and the pre-publication review — lands on an append-only, tamper-evident hash chain, Merkle-anchored to external timestamping services nightly. The methodology served today is the artifact with SHA-256 08cbdb46beed306a430b35c4d6d5e1a03d2a1d1d29bfef65fa5105cf53820381, uploaded 2026-07-12; the board's figure routes withhold themselves if the served document ever differs from the reviewed one.

What to take away — and what we deliberately don't do

The takeaway is a habit, not a number: every figure should arrive with a way to check it and a statement of what it does not say. That is the whole methodology — proofs where the chain permits them, captured documents before parsed ones, ratios only inside a single document's stated scope, and an evidence trail that outlives any correction.

Just as deliberate is what stays out of scope. The board carries no solvency verdicts, no price or depeg data, no predictions, and no rankings that reach beyond what the documents themselves state. When a figure is missing, that gap is published as the finding rather than papered over — because the moment a measurement service starts filling silences with estimates, readers lose the ability to tell which of its numbers were ever measured at all.

Last updated: Timestamps reflect the underlying data — when a figure was captured or a report was published — never when a page was built.

Frequently asked questions

What does the STORAGE-PROVEN source tier mean?

The token contract's total-supply storage slot was read with eth_getProof and the Merkle-Patricia proof was verified locally against the block's state root. The slot was pinned only after a probe found exactly one slot equal to totalSupply(), and that equality is re-verified on every snapshot.

Why does ReserveBeat never divide reserves by on-chain supply?

A ratio of figures from different sources at different instants manufactures precision the underlying documents never stated. A coverage ratio here only ever divides two figures the same issuer attestation states at the same as-of date; on-chain supply serves as an independent cross-check, not a ratio input.

Can the board show a figure its review has not covered?

No. Every figure route checks that a pre-publication review artifact covers the exact methodology document being served; if the served and reviewed methodology hashes differ, the routes withhold their figures rather than render anything unreviewed.