A pinned snapshot, one live Ed25519-signed endpoint report, and the public key behind the signature — so every figure in the grant submission can be checked independently, not taken on trust.
The exact JSON behind these numbers, frozen at submission time. The live endpoint moves; this file does not.
stats-snapshot.json → live /v1/stats →A fresh live 402 probe (not cached) + settlement reality from the ledger + R1–R4 anomaly view, signed with Ed25519. This example returns a WARN — the endpoint declares the legacy base network id instead of eip155:8453. That is the conformance gap the observatory exists to surface, shown honestly rather than hidden.
The Ed25519 public key that signs every report — published so signatures are independently checkable, not asserted.
b1040b0602fbd9996306e33fe179fe570a7b0f32ed4a538aa11e8c33a350e33c.well-known/x402-verify →
Take the report body above the attestation block, hash it, and check the Ed25519 signature against the published key:
sha256 of report body == attestation.sha256 Ed25519.verify(pubkey, signature, sha256) == true
The pubkey in the report matches .well-known/x402-verify exactly. Same key, end to end — and you can run this live in the Proof Room.