ReserveProof · status

Are the proofs up?

Every custody proof on both testnets, the Morpho oracle wrapper, the epoch publisher (every 3 days), the hourly watchtower that re-publishes if a run is missed, and the publisher's gas. Proof health is read from the chain; run history comes from GitHub Actions.

Verify every claim JSON feed

Reading both chains and the run history…

How this is judged

Down: a custody proof is failing, an equivocation is proven, a balance challenge is past its deadline, an ExitRight claim defaulted, the Morpho wrapper is reverting, or a gated consumer is frozen.
Degraded: a proof has under 48 hours before it goes stale, a dispute or challenge is open, the last publisher or watchtower run failed, no watchtower check ran in the last 3 hours, or the publisher has under 0.001 ETH.
GitHub runs cron workflows best-effort and skips many slots, so a small scheduler workflow dispatches the watchtower on the hour, with the cron as a backup. Any gap left in the hourly bar is shown as it is rather than hidden. The watchtower re-publishes whenever a proof has under 72 hours left, so a late check still lands days before anything goes stale.
Sources: loadRisk reads of both testnets (the same data as /risk), the deployer's balance, and the GitHub Actions API for watchtower.yml and ops-epoch.yml. Cached for 2 minutes; the page refreshes every minute.