Offline verifier for AINumbers Evidence Envelope v0.1 receipts. Given a receipt JSON it recomputes the RFC 8785 JCS signing preimage, verifies the Ed25519 (EdDSA) signature against the did:key resolved from issuer_id and signatures[].kid, checks that every hash field is a sha256:-prefixed 64-character hex string, and, when a prior receipt is supplied, recomputes previousReceiptHash to prove the chain link. Verify-only: it never issues a receipt, never contacts a transparency log or registry, and never resolves a DID document over the network.
compliance_controlZero PIIClient-side only
🔒 All inputs are processed locally in your browser. No data is transmitted. Do not enter real personal data — use synthetic or anonymised inputs only.
Scope & reliance
Every verdict below is RECOMPUTED from the receipt's own bytes. No self-claimed hash and no self-claimed verdict field is trusted (STANDING-ORDERS #34). The Evidence Envelope v0.1 format this node checks is an AINumbers-internal ratified artifact (research/EVIDENCE-ENVELOPE-V01-RATIFIED-2026-08-20.md), not a third-party published standard or regulation, so the node declares standards_basis: not_applicable rather than citing external clauses. What the node does NOT do: it issues nothing, signs nothing, resolves no DID document over the network, and consults no transparency log, so a signature that verifies here proves the receipt bytes match the key named inside them and nothing about whether that key is authorised. The Ed25519 and SHA-256 primitives are the vendored noble bundle inlined below, byte-identical to the kernel that runs server-side, because the zkVM guest has no WebCrypto. No formal correctness proof exists for this node yet (compute_proof_ready: deferred); see the proof-status note below the results.
Policy Parameters (JSON)
Result
Proof status
This node ships compute_proof_ready: deferred. No formal correctness proof has been produced for this kernel; the result above is a deterministic recompute, verified by a property-test floor, not a proven one.