EVE ProofEvidence
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.
Anyone holding the public key can verify a signature. The private key never leaves the signer; verification needs no secret and no live service.
A certificate, the public key, and a stock crypto library — nothing else. Confirm authenticity air-gapped, with zero dependency on EVE infrastructure.
Key ids are embedded in every certificate, so rotation never orphans old evidence. A record signed today verifies years from now.
From the API response, an exported evidence pack, or your own retained store. It is self-contained.
Available at a stable endpoint and pinnable. Key ids are embedded in every certificate so rotation never orphans old evidence.
Canonicalize the payload (RFC 8785), check the Ed25519 signature against the public key. Valid means the bytes are exactly what was signed.
Confirm prev_hash linkage and the Merkle inclusion proof to prove the decision sits, unaltered, in the published history.
This runs entirely in your browser. Tamper with the certificate and watch verification fail.
Verify a live decision certificate in your browser — then hand the evidence to your own auditor and watch them verify it without us.