Verify a record without asking us.
Each record keeps its method version, evidence status and commitment. The v1 archive uses FNV-1a; the v2 working method specifies SHA-256. They are not interchangeable.
Evidence status, not marketing numbers. The local v1 chain contains exactly 20 simulated records. A separate CoffeeJeV platform publishes one live related-party reference record. None of these is an independent certification decision or proof of commercial adoption.
Recomputable FNV-1a chain
Open the original 20-record viewer, inspect every payload, test tampering and verify head 54980f3d. The evidence files are unchanged.
Open v1 registry →CoffeeJeV interoperability
CJ-CN-2026-0712-63E7 · 0.1951 kgCO₂e/plantlet · grade B. CoffeeJeV is founder-affiliated; this record demonstrates interoperability, not independent validation.
Inspect source record →No production claims implied
CJV-MTH-2.0 is a working specification. The calculator below demonstrates a SHA-256 digest only; it does not issue a registry record or validate source data.
Read the v2 method →Archived v1 specification and verifier: CJV-MTH-1.0 evidence archive →
Compute a v2-format commitment locally
Enter a canonical payload. This browser calculates SHA-256 using WebCrypto; no input is transmitted. For v1 records, use the FNV-1a archive instead.
The ugly history stays public
A revoked record retains its identifier, original commitment, date and reason. A register that deletes its failures makes current records harder to trust, not easier.
Cite the state you checked
A meaningful citation names the record count, method version and chain head alongside the date. The registry changes; your verification should identify the state it referred to.