Verification correction · July 23, 2026
Commit Regimes artifact mapping
We found and corrected a mismatch between the PDF served by this site and the PDF hash committed on Sepolia. Both byte-distinct builds are preserved below.
Canonical anchored v1
SHA-256 37b1ee34671b39b1f624b76763b9e6e8eaec6825e57882e3cc3ac46669eb264d
Sepolia committed these exact bytes on March 25, 2026. The OpenTimestamps proof was created post-hoc on July 23, 2026; it closes the current dual-proof lineage but does not replace or backdate the Sepolia priority record.
What happened
The research card displayed the canonical hash and linked the correct Sepolia transaction, but its download URL served a later April 3 re-typeset build. That build hashes to 46e238192f025416b035faf10ed33937aec29521508c6910d9112cd51d27f67a. Its June OpenTimestamps proofs correctly bind those later bytes.
The two files have the same title but are different byte artifacts. We make no equivalence claim between them. The canonical v1 URL now serves the exact artifact committed on-chain, while the displaced build and its proof lineage remain available for direct comparison.
Preserved April 3 build
SHA-256 46e238192f025416b035faf10ed33937aec29521508c6910d9112cd51d27f67a
Repair
We restored the exact on-chain artifact, retained both builds and proof histories, and added a deployment check that recomputes every public paper hash and compares it to the page and OTS-bound digest. Production is also checked against Sepolia calldata after release.
This record is append-only in meaning: future corrections will create a new dated record rather than silently changing this account.