News · 12–13 November 2026
We re-ran xChk's receipt verifiers and recomputed its public Black Box Report
An xChk registry keeps a record of each action that a verified person approved. For each record it issues a receipt signed with two keys (Ed25519 and ML-DSA-65) and a SCITT signed statement over the record's hash. xChk publishes two offline verifiers for them in the xchk-scitt repository, and a public evidence report on one incident, the Black Box Report of 24 August 2026. We checked both from public material only.
What we ran
-
The repository at commit
e956901, run as its README documents: the receipt verifier with--require-approvaland the registry's key document, and the statement verifier with the receipt bundle and the key document. Both passed (exit 0), and the 11 tests passed. - 4 inputs changed on purpose: one character in the record, one flipped bit in the statement's signature, one flipped bit in its payload, and a statement checked without any key. The verifiers refused each one (exit 1).
- The public report: every record hash, record chain link, seal hash, seal chain link and Merkle root, recomputed with code written here from the rules xChk publishes in the report's own in-browser verifier. Record hashes 6 of 6, record links 5 of 5, seal hashes 12 of 12, seal links 11 of 11, Merkle root 1 of 1. Our code runs none of xChk's code, and it also checks the seal links, which the in-page verifier does not.
The first run was on 12 November 2026. On 13 November we ran it again from an empty directory with every output kept: the scripts, the full output of each step, and the size and SHA-256 of every input, including the report (902,822 bytes). Every result was the same as the day before. The scripts and outputs are available on request.
What this does not cover
We did not check the blockchain anchors, the SLH-DSA root signature, or the signature of the report's incident-package token, and xChk's registry code is not public. A passing check shows that the published receipts, statements and report are consistent under xChk's published keys and rules; it does not show that any recorded command ran as recorded. The receipts, the verifiers and the report are xChk's work. This is verification of third-party software and evidence, not peer review, and not an endorsement in either direction.
xchk-scitt on GitHub ↗ · The Black Box Report ↗ · Track record →