Legal evidence chain
Cryptographic provenance for every published version of every QENEX legal document
Every version of every QENEX legal document is SHA-256 hashed at publication, signed with the operator’s Ed25519 key, pinned to IPFS for content- addressed retrieval, and anchored into the public Bitcoin timechain via OpenTimestamps. An auditor, regulator or court can recompute the hash from the HTML in front of them, verify the signature against the public key below, and verify the OpenTimestamps proof against any Bitcoin full node. The result is an evidence chain QENEX itself cannot tamper with: even we cannot retroactively change which document was in force on date X.
| Document | Version | SHA-256 (prefix) | Effective | IPFS pin | Bitcoin anchor |
|---|---|---|---|---|---|
| terms | v1.0 | 65888d5bec61fb4d… | 2026-05-14 | IPFS QmbNkNWDtm5wQu… | OTS ✓ |
| privacy | v1.0 | c54c94f103aff76f… | 2026-05-14 | IPFS QmdrPa2eUmB6xY… | OTS ✓ |
| acceptable-use | v1.0 | 037d3da4b928ee88… | 2026-05-14 | IPFS QmR4dUU1NrvYe2… | OTS ✓ |
| dpa | v1.0 | cbfc1ef45c4003ff… | 2026-05-14 | IPFS QmZk1EPBLSy3yE… | OTS ✓ |
| sla | v1.0 | 822a90b4582b6c7c… | 2026-05-14 | IPFS QmdsThJFSqVjJd… | OTS ✓ |
| cookies | v1.0 | 3e7104dafde2e3e8… | 2026-05-14 | IPFS QmTKeZAVJsgNxU… | OTS ✓ |
| subprocessors | v1.0 | 22c51c65b9174207… | 2026-05-14 | IPFS QmXp9F6yEW5GYh… | OTS ✓ |
Operator public key (Ed25519)
+zYIOMGboQaj1dFM640fX5E0fvCQ6bt8xIAo4BipI9o=
Same key signs the daily evidence bundle and DNS attestations. Verify
signatures using any standard Ed25519 implementation (libsodium, NaCl,
Python cryptography, Go crypto/ed25519, etc.).
Signatures on legal documents are made over the raw 32-byte SHA-256 of
the document content (not the hex-encoded form).
How to verify in court
- Obtain the HTML version of the document you want to verify (from the live URL, or from the IPFS gateway using the recorded CID).
- Compute its SHA-256 hash; compare to the published hash on this
page or via
/api/v1/pulse/legal/version-record/<slug>. - Verify the Ed25519 signature against the operator public key above.
- For the timestamp claim: take the SHA-256 and the corresponding
.otsproof, runots verify; the tool reports the Bitcoin block height in which the hash was committed and the block’s timestamp.
Optional belt-and-braces: a qualified electronic time-stamp from a regulated EU Trust Service Provider (eIDAS Regulation 910/2014, Art. 42). QENEX is evaluating QTSPs for the Compliance tier; until that contract is executed, the IPFS + OpenTimestamps chain provides strong but non-qualified evidence in all jurisdictions.
Programmatic access
GET /api/v1/pulse/legal/version-record — catalogue of every version.
GET /api/v1/pulse/legal/version-record/<slug> — full history for one document.
GET /api/v1/pulse/dns-attestations/public-key — operator public key.