GET /api/sentinel/state just now, so the figures above are the last
known live values rather than current ones. Nothing shown is simulated — this
instrument runs in mode: "live" per draft-reilly-mws-01 §10.5 and does
not synthesize ledger activity when the pipeline is unreachable. Polling continues
automatically; the badge returns to LIVE on the next successful fetch.
Append-only. Fingerprint re-verification, anchor re-verification, resolution checks, drift detection, and Stage-10 repairs, as they happen.
Each artifact's layer coverage and most recent full verification.
| ARTIFACT | SHA-256 | L1–L5 | LAST VERIFIED |
|---|
No claim on this page requires trusting the operator. Pick any artifact:
1 Fetch it from a fallback layer and hash it —
sha256sum <artifact> — the digest matches the ledger or it doesn't.
2 Check its Bitcoin anchor —
ots verify <artifact>.ots — the proof verifies against the chain or it doesn't.
3 Resolve its DOI at zenodo.org/search?q=reilly and its draft record at datatracker.ietf.org — it resolves or it doesn't.
4 Check that this ledger was never rewritten — /api/sentinel/ledger/verify — every event digests the one before it, so a single altered row breaks every link after it. Poll /api/sentinel/events twice and walk the chain yourself if you would rather not take the endpoint's word.
Independent operators: the cross-verification procedure is specified in draft-reilly-mws-01 §12.2. Run it against this corpus and publish your records.