Verify the record yourself
Every SONAR pre-registration artifact is anchored to the Bitcoin blockchain via
OpenTimestamps — a permissionless, account-free
proof that the file existed no later than the naming block's timestamp. You can confirm this
with no trust in us. Download each file and its .ots proof below and run the two
commands.
| Artifact | SHA-256 | Bitcoin block(s) | Download |
|---|---|---|---|
| shadow_adjustments.json | 663025e396c111ec16b809343d9cc09d9fa251102448996319d2ed77fc38a101 | 957350, 957352, 957354 | file · .ots |
| hypothesis_log.md | 3ce29f1c026bfae316d68fd3aae8cc0fc0f8bf775a28b2354e5f8844e6c2aad0 | 957359, 957360 | file · .ots |
| interpretation_addendum_2026-07-10.md | adce7c44a95184a1b58de48c443cbe8643d79526f29f2698491b35710af714d1 | 957426 | file · .ots |
| confidence_shadow_preregistration_2026-07-10.md | 172a868e120caeb55062efc627a4a66301c1e4076c7b633c39c3388660d5b63f | 957441, 957442 | file · .ots |
| county_pair_methodology_2026-07-10.md | 2ec36a4c3a46c6bcdd61126b7cb02a7e604a779a9844f3b6bbc114d976e59567 | 957484, 957487, 957512, 957522 | file · .ots |
| identity_linking_2026-07-11.md | 51d7f3bdf086d12c8b553f95480a5c53b2f67d38d5e1fbb95dcec6a5565287d8 | 957595, 957596, 957603 | file · .ots |
| identity_linking_correction_2026-07-11.md | 2374ffa452a7d2f2b5056de1253afd05986689831fc105f5f7e5b876daf0bea5 | 957638, 957640, 957653 | file · .ots |
| comparator_addendum_2026-07-13.md | f2ff50545bd620e3f6f46647f34c09ca5c127e7505ecd2ccb67f14c11c2ba24f | 957856, 957863, 957867, 957884 | file · .ots |
| zm_weighting_variants_2026-07-15.md | 731958081555e86df6a9774779c62ea7e05698d4f2538ff210bd46deb9a384fd | pending | file · .ots |
Check it (no account needed)
- Confirm the file content matches its published SHA-256:
shasum -a 256 <downloaded-file> # must equal the SHA-256 in the table above
- Verify the OpenTimestamps proof against Bitcoin (needs the
otsclient and, for full verification, a Bitcoin node):ots verify <downloaded-file>.ots # reports the Bitcoin block time the content is proven to predate. # Without a node, `ots info <file>.ots` still shows the block number(s).
The full anchoring record, including calendar servers and how each proof was upgraded to a Bitcoin block, is in ANCHORS.md. If any file's SHA-256 fails step 1, the record has been altered — which is the point.