Verify an OVERT proof — the AI attestation verifier
The whole point of an OVERT receipt is that you don’t have to trust the party who gave it to you. A verifier checks the cryptographic claims yourself — offline, with no call back to Glacis.
What a verifier checks
Section titled “What a verifier checks”A complete OVERT receipt verification confirms:
- Signature — the receipt is an Ed25519 signature over RFC 8785 canonical bytes, made by the claimed key.
- Canonical hashing — the content hashes match, recomputed independently (cross-runtime: the same bytes verify from Rust, TypeScript, or Python).
- Chain inclusion — the receipt is included in the notary’s RFC 6962-shaped transparency log, with a valid inclusion proof.
- Non-egress — the receipt carries only hashes and line-ranges, never raw prompt or response text.
If any check fails, verification fails closed.
Verify today (offline receipts)
Section titled “Verify today (offline receipts)”pip install glacispython -m glacis verify receipt.jsonWhy a neutral verifier matters
Section titled “Why a neutral verifier matters”A “system of proof” only works if the proof is checkable by someone who distrusts the vendor. That’s why the verifier is being built as a vendor-neutral, Apache-2.0 tool referenced by the OVERT standard itself — independence of verification never requires trusting Glacis.
Python SDK quickstart Install the client and verify offline receipts today.
AI attestation, explained What attestation is, and how it differs from TEE/hardware attestation and model signing.