AI Decision Evidence

Verify it yourself —
no trust required

Trust is not a feature. EVE Proof is built so the party reading the evidence never has to take our word for anything. A certificate, the published public key, and a stock crypto library are all that is required — on a disconnected laptop, today or in seven years.

The Property

Three things make it real

🔑

Asymmetric (Ed25519)

Anyone holding the public key can verify a signature. The private key never leaves the signer; verification needs no secret and no live service.

🔌

Truly offline

A certificate, the public key, and a stock crypto library — nothing else. Confirm authenticity air-gapped, with zero dependency on EVE infrastructure.

Durable

Key ids are embedded in every certificate, so rotation never orphans old evidence. A record signed today verifies years from now.

How To

Four steps

1

Receive the certificate

From the API response, an exported evidence pack, or your own retained store. It is self-contained.

2

Fetch the published public key

Available at a stable endpoint and pinnable. Key ids are embedded in every certificate so rotation never orphans old evidence.

3

Verify the signature locally

Canonicalize the payload (RFC 8785), check the Ed25519 signature against the public key. Valid means the bytes are exactly what was signed.

4

Walk the chain (optional)

Confirm prev_hash linkage and the Merkle inclusion proof to prove the decision sits, unaltered, in the published history.

Try It

Verify a real certificate now

This runs entirely in your browser. Tamper with the certificate and watch verification fail.

Keep Reading

Related

See a real certificate verify

Verify a live decision certificate in your browser — then hand the evidence to your own auditor and watch them verify it without us.

FAQ

Common questions

Can I verify without contacting EVE?
Yes — that is the point. Verification needs only the certificate, the published public key, and a standard crypto library. No callback, no account, no network.
What if EVE NeuroSystems no longer exists?
Old certificates remain verifiable against the public key that signed them. The verification procedure is independent of EVE's continued operation.
Which library do I need?
Any Ed25519 implementation — libsodium/PyNaCl, Python cryptography, Node Web Crypto, or the open-source eve-verify package. The math is standard.
One Control-Plane Stack

Governance decides. Enforcement acts. Proof attests.

The EVE Control-Plane Stack

Explore the ecosystem