Technical Standard v1.0

Cryptographic Evidence Bundle Specification

A self-contained evidence bundle built on canonical JSON, SHA-256 and RFC 3161 timestamps.

Independent Verification

Independently Verifiable Evidence Architecture

Evidence bundles generated by HashEntry are designed so that third-party auditors and independent tools can verify their integrity and timestamp without access to HashEntry servers or databases. What weight that evidence carries is decided by the authority reviewing it.

No HashEntry server required
Canonical JSON

Canonical JSON Format

In ordinary JSON, key order and whitespace can change the hash. HashEntry serializes consent records deterministically — keys sorted, UTF-8, no extra whitespace — so the same record always yields the same SHA-256 digest. The exact rules are in the bundle's verification notes.

Deterministic Key Sort & UTF-8 Encoding
Bundle Structure

Evidence Bundle File Architecture

The exported .zip archive contains 6 essential files that can be independently inspected and verified:

consent_data.jsonCanonical JSON

User consent preferences, version identifier, timestamp, and pseudonymized client context.

metadata.jsonSystem Metadata

Digest algorithm declaration (SHA-256), TSA authority identifier, and evidence spec version.

checksums.sha256Integrity Manifest

SHA-256 checksums of all package contents (verifiable via shasum -c).

tsa_token.tsrRFC 3161 Timestamp

Binary ASN.1 DER timestamp token signed by an RFC 3161 Time Stamping Authority.

ca_chain.pemX.509 Certificate Chain

Public certificates of the root and intermediate Certificate Authorities that signed the timestamp.

proof_verification.txtText Verification Summary

Human-readable verification instructions and audit checklist for compliance officers.

Verification Algorithm

Step-by-Step Independent Verification

Follow these steps to verify the evidence bundle using standard open-source tools:

01

Verify File Checksums

Ensure none of the files inside the bundle have been modified or corrupted:

$ sha256sum -c checksums.sha256
02

Compute Consent Data Digest

Generate the SHA-256 hash of the canonical consent_data.json file:

$ openssl dgst -sha256 consent_data.json
03

Verify RFC 3161 Timestamp Signature

Verify the cryptographic timestamp token against the Root CA and match the digest:

$ openssl ts -verify -data consent_data.json -in tsa_token.tsr -CAfile ca_chain.pem

Automate with Open-Source CLI Verifier

We are preparing an open-source terminal CLI (hashentry-verify) so you can run all verification checks automatically in your own pipeline.

CLI Verifier — Coming Soon

Strengthen Your Compliance Evidence Today

Start with the free plan. No credit card required.