Verify
Check it yourself.
This runs entirely in your browser — your files never leave your machine. It makes exactly the same three checks as our command-line tool: that the file is byte for byte the one we signed, that the numbers add up again when they are recomputed from scratch, and that it links correctly to the certificate before it.
Inputs
Check a file on your own machine.
Pick the signed certificate and the public key you were given separately — separately on purpose, so that one of them being tampered with cannot go unnoticed. If the certificate refers back to an earlier one, add that too.
Only needed if this certificate follows an earlier one.
Results
What the checker found.
We ran this for you when the page loaded. Run it again, or check your own files above.
Verifying the published study 001 certificate…
The recomputed numbers, step by step
Every number here was worked out again from the data in the file. None of it was copied across from what the monitor happened to have saved.
| Evidence epoch | Blocks replayed | Observations | Log e recomputed | Alarm index | Verdict |
|---|
CLI
Or do it from the command line.
Our Apache-2.0 licensed Rust tool does exactly the same work offline. Download the study 001 certificate and trusted public key, then run:
cargo build -p actuary-cli
actuary verify certificate.json --pubkey public-key.hex
No database, no server, no network connection — and no need to ask us anything.