Reserve evidence, ready for examination

1. 1

   Capture

   Issuer-published attestation reports are fetched from the issuer's own site, hashed on arrival, and appended to a tamper-evident chain before anything parses them. Token supply is measured independently at a quorum of Ethereum RPC providers rather than read from an aggregator. A parser that meets an unexpected layout refuses the document rather than guessing at it.

2. 2

   Reconcile

   Each day the captured reserve evidence is set against measured liabilities at the scope the source document states, and the result is recorded with the inputs it was computed from. Nothing is netted, adjusted, or rounded into agreement: a figure the source does not state stays absent, and a run that cannot complete writes nothing rather than zeros.

3. 3

   Hand over the bundle

   Each month the captured records, their reconciliations, and the hash chain and timestamp anchors covering them assemble into one evidence bundle for whoever is examining the period. The bundle carries its own manifest, so a recipient can re-derive every hash and check every anchor without ReserveBeat in the loop. Corrections travel as supersessions, and both sides of one keep their anchors.

The tour is not open to the public in this deployment, so this page links to it nowhere rather than pointing a reader at a page that would not answer. What can be read without it is the whole published record: the methodology in full, every parsed attestation report beside the issuer document it was read from, and the log of every correction ever made to one.

• The methodology publishes in full, verbatim and hash-anchored, and figures publish only under a current pre-publication review of it. When that review lapses or the methodology changes, pages say so rather than serving unreviewed numbers.

  Methodology→

• The status page reports, live, whether the public API is answering, whether the review covers the served methodology, when the registry chain was last anchored, and how recently data was captured — the same self-check ReserveBeat applies to the issuers it tracks.

  Status→

• The data definitions page gives the exact arithmetic behind every computed metric: its inputs, its rounding, and what the result does not mean, so any figure published here can be re-derived from the same sources.

  Data definitions→

• Every parsed attestation report has its own page carrying the reserve composition and as-of dates the issuer's document stated, and the revision log lists both sides of every correction ever made to one.

  Revisions→

• Control criteria→
• GENIUS Act→

Every figure traces to a document or a contract: attestation reports published by the issuer and captured from the issuer's own site, and token supply measured at a quorum of independent Ethereum RPC providers. Each captured document is hashed before parsing and its hash is anchored to an independent timestamp authority, so the record can be shown to predate any later argument about it. The public pages here run on that same pipeline — the site is its own worked example.

The fastest way to judge this is to check it: read the methodology, open a parsed attestation report and follow its figures back to the issuer's own document, then read the status page to see what is being served right now. The tour shows the rest of the pipeline end to end.