Verification

Anchored hours

Summary. 2,714 hours sealed, 3 hours anchored since October 23, 2026: per hour, the digest's SHA-256, the previous digest's SHA-256 and a token from an independent time-stamping service (RFC 3161), with the command that checks it. Machine-readable: https://noxfze.com/verify/anchors.json.

View as Markdown

An hour sealed is one UTC hour of one recorded channel, sealed into its hash chain and checked by a measurement separate from its recorder. Every UTC hour, Nox FZE writes one digest of its record. The digest lists the SHA-256 of the newest manifest of every hash chain and of the other records it covers. It also carries the SHA-256 of the digest before it, so each digest chains to the hour before. The digest's SHA-256 is then time-stamped by an independent time-stamping service (RFC 3161). The digest itself stays private, because it names what it covers; its SHA-256 and the token are published here.

Check a token

A token proves that a digest with the listed SHA-256 existed no later than the time inside the token, unchanged since then. The token carries its issuer and the time. Three commands, with OpenSSL:

curl -sO https://noxfze.com/verify/anchors/2026-10-23T1400Z.tsr
curl -sO https://noxfze.com/verify/anchors/ca.pem
openssl ts -verify -digest dbb9041c7e4d76d8258215b1f793f4e353c3eef755f67e20f9e77d1950c41dec \
  -in 2026-10-23T1400Z.tsr -CAfile ca.pem

Verification: OK and exit status 0 mean the token was issued under that certificate and covers that SHA-256. Any other row checks the same way with its own hash and token. openssl ts -reply -in 2026-10-23T1400Z.tsr -text prints the time and the issuer.

Anchored hours

The newest first. The same ledger, machine-readable: /verify/anchors.json.