Company
Contact
ReserveBeat publishes one inbound address, contact@reservebeat.com, for reports that a figure on this site is wrong. This page sets out what such a report needs to identify, why the issuer's own published document decides the question, how quickly a report is acknowledged, and how a correction reaches the public record once one is made.
Report an incorrect figure
A report that a published figure is wrong becomes actionable when it identifies the figure exactly: the page the figure appears on, the figure itself with the as-of date rendered beside it, and the passage of the issuer's published report — or the on-chain reading — that states something different.
Source documents decide
Source documents decide. Every figure on this site is rendered verbatim from an issuer-published attestation report or measured from a public blockchain, so a disagreement between a page here and the document it was read from is a defect in ReserveBeat's reading of that document, and the document wins.
Methodology · Data definitions
How a correction lands
A correction is made by supersession, never by silent edit: the corrected record is published alongside the record it replaces, both stay retrievable, and each keeps its own timestamped evidence. A figure that changes therefore leaves a trail rather than quietly becoming a different number. Revisions
Where to send a correction
A report that a figure published here is wrong, or a question about how one was read, goes to contact@reservebeat.com. A report is acknowledged within five business days — an acknowledgement that it arrived and was logged, not a finding by that date. Any correction that follows is published by supersession, alongside the record it replaces, never as a silent edit.
Postal address
Postal address: PO Box 620672, Charlotte, NC 28262.
API access and API bug reports
The same address takes questions about buying compute units, Enterprise arrangements, and reports of an API bug. A bug report should quote the request id — error.request_id in a refusal body, or the X-Request-ID header on any response — which names that exact request in the service's own record.
About the subscription form
The subscription form on this site is an attestation-alert list, not a message channel. An address submitted there becomes active only after a confirmation click, is used to send alerts for the token it was submitted against and nothing else, and every alert carries a one-click unsubscribe link.