Verify an AI Decision Certificate — In-Browser

What You're Seeing

No trust, no network, no vendor

🔑

Real cryptography

Verification uses the browser's Web Crypto API to check a genuine Ed25519 signature — not a simulation.

🔌

Fully offline

The certificate and public key are processed locally. Nothing is sent to EVE or anyone else.

⚠

Tamper-evident

Change one field and the signature no longer matches the bytes — verification fails, visibly.

Under the Hood

What happens when you press Verify

The verifier does exactly what an auditor would do on an air-gapped machine — there is no shortcut and no server involved:

Strip the signature. The signature field is removed, leaving the payload that was originally signed.
Canonicalize. The remaining payload is serialized with the RFC 8785 JSON Canonicalization Scheme — sorted keys, no whitespace — so the exact bytes are reproducible.
Verify the Ed25519 signature. Using the browser's Web Crypto API, the signature is checked against the published public key over those canonical bytes. A match proves the payload is byte-for-byte what was signed at decision time.
Fail loudly on tamper. Because the signature commits to every byte, changing a single character — a verdict, an amount, a timestamp — makes verification fail. There is no "almost valid".

The same procedure runs in the open-source eve-verify Python, TypeScript, and CLI tools, and in the downloadable verify_sample.py. Identical inputs, identical result — that is the point of offline verification.

Keep Reading