GENIUS Act · Continuous Monitoring

Continuous Reserve Watch

A weekly automated tick takes a stablecoin issuer's disclosed monthly reserve report, replays it through the live GENIUS Act reserve-disclosure checker, and produces a signed, anchored, replayable receipt, all without a human re-running the check by hand. This page explains exactly what that receipt proves, and what it deliberately does not.

Weekly Cron Hash-Anchored Receipt Byte-Replayable Zero PII

🔒 All inputs are processed locally in your browser. No data is transmitted. Do not enter real personal data — use synthetic or anonymised inputs only.

What this is not: the watch checks the reserve-report FIELDS the issuer disclosed (composition percentages, attestation cadence, auditor type) against the GENIUS Act checklist. It does not, and cannot, cryptographically verify that the underlying PDF or bank statement is authentic, unaltered, or truthful. That distinction is load-bearing: see the proof-scope table below.

How It Runs

Weekly tick, four steps

Timed to land ahead of the GENIUS Act rulemaking-final window. Every fire is independent and replayable, with no hidden state between runs.

Cron fires on the shared weekly substrate

A Cloudflare Worker scheduled trigger (the same substrate that also drives the AI-Act evidence cron below) wakes on a weekly cadence and emits a CloudEvents envelope marking the tick.

Ingest the disclosed monthly reserve report

The tick reads the issuer's most recently disclosed reserve composition and attestation fields, the same shape a human compliance reviewer would read off the published report.

Run the live checker kernel

The disclosed fields are passed to check_genius_reserve_disclosure (ART-275), the same deterministic kernel that powers the interactive composer. Output carries an execution_hash over the exact input/output pair.

Anchor the receipt and emit the envelope

The result is signed and archive-timestamped through the shared anchor lineage, then wrapped in a CloudEvents envelope so any downstream consumer can subscribe without polling.

Proof Scope

What is proven, what is not

Claim	Status	Why
The checklist ran against these exact disclosed fields	Proven	`execution_hash` commits to the exact input/output pair; any third party can replay the kernel and get a byte-identical result.
The check result was not altered after the fact	Proven	The receipt is anchored (signed + archive-timestamped) at generation time.
The disclosed reserve-report fields are truthful	Not proven	The watch checks disclosed fields against the checklist; it does not audit the issuer's actual reserve holdings.
The source PDF/bank statement is authentic or unaltered	Not proven	ART-275 never claims to cryptographically verify a source document, only the checker's own disclosed-field input and output.

Continuous Reserve Watch

Weekly tick, four steps

What is proven, what is not

Explore adjacent tooling

Reserve Disclosure Checker (ART-275)

Reserve Attestation Precheck

AI-Act Evidence Cron

OpenChainGraph Hub