Proof
Every number here comes from a recorded run on real hardware, sealed with a hash you can check.
On the right: an actual result from our independent verifier, a tool that contains none of our code.
INDEPENDENT VERIFIER · AUG 24, 2026
Kernel-to-silicon proof kit
KIT SHA-256
0843262c04d1bc6b9dc66be15ac94515ad44e1a5627562b19d078cd6bbe22342
The runs
Five runs. Each one on its own.
937,958 receipts. Not one missing.
27,587 passes in a row, nonstop for eight hours, zero fail-opens. The AMD chip signed off on the final result.
AMD EPYC Genoa · SEV-SNP
July 2026
commit b74334043b54…
3,000 requests. Only 4 had permission. Only 4 ran.
On an NVIDIA H100 with confidential computing on. GPU and CPU proved they were genuine first.
Azure H100 confidential VM
September 10, 2026
sha256 a230d05a9725…
462 hospital scenarios. 462 right answers.
From a clean start, including a conflicting repeat request refused with nothing run.
Bare metal · SEV-SNP
September 13, 2026
sha256 05d96988a3bc…
One action, traced from the AI to the chip.
Request, permission, real action, final receipt. Then permission pulled, and the same action denied.
AMD EPYC · SEV-SNP
August 24, 2026
sha256 0843262c04d1…
Installed on 3 fresh servers. Zero code changes.
Install, reboot, uninstall. Clean every time.
Ubuntu 24.04 · Azure
August 18, 2026
sha256 8ed892e72906…
Try to cheat it
Fake a receipt. See what happens.
Four real receipts, signed in your browser a moment ago. Verify them first, then try to cheat.
- Signing…
Real SHA-256 and Ed25519, running in your browser. In production, the same check runs at the operating system on your hardware.
Run the verifier yourself.
Every evidence kit ships with a standalone verifier. It runs offline and contains none of our code.