CertNode offline receipt verifier

Runs the reference @certnode/verify implementation in your browser — CertNode’s servers are not consulted for any verdict. Works from file://. Format: cn.receipt.v1 specification · vectors: conformance/v1.

What this proves (and doesn’t): verdicts are per layer — signature authenticity, content integrity, independent RFC 3161 time, Bitcoin anchoring (header-verified, explorer-backed unless you check against your own node), each labeled separately. Receipts are self-authenticating under FRE 902(13)/(14), subject to certification and tribunal review. The internal CertNode seal is issuer-attested only and never counts toward a verdict.

Receipt JSON — the full receipt object ({ id, data, hash, signature, certnode_timestamp, rfc3161_timestamp, bitcoin_anchor, … }) Expected receipt ID — anti-swap bind; auto-filled from receipt.id, override if you obtained the id elsewhere Original content (optional — re-hashed and compared to the signed contentHash claim) JWKS JSON (optional — paste certnode.io/.well-known/jwks.json for fully offline verification; if empty and network is allowed it is fetched once)

Allow network — fetch the JWKS if not pasted, and check the Bitcoin anchor against two independent block explorers (blockstream.info + mempool.space, which must agree). Uncheck for fully offline operation: paste the JWKS, and the Bitcoin layer reports UNKNOWN instead of consulting explorers.