Blocklore
Esc

Type to search every published claim: statements, sources and topics.

Enter opens the claim; with no match, suggests the questionUp and down to move
976,842

Every snapshot

Snapshot 1: 228 claims

In block 976,778
Taken
20 Nov 2026, 18:50 UTC, block 976,771
Root
8cad119ea308b39995b648acd31032756a1abe9e1236055540472fcc3408f4c7
Previous
None, this is the first
Commit
2b799307767cc51d7faeeefeed7ed3a88cf72b48
Timestamp
In block 976,778: the file existed before that block was mined. Its header's merkle root is 3e973d30ad16ee4ed9e70056f71fc2bafdd82b7c35ffb04489f3c412d54fb491.
Files
1.json, 1.json.ots (SHA-256 of the file: f08273b2bcc08ef02ad4c187bc940f65c11aeaa3b9d5e4d55186c9e5cc691671)

Check a snapshot yourself

The verifier in the repository recomputes everything from the claim files and checks the proof against a Bitcoin block header, from your own node when bitcoin-cli answers, otherwise from two block explorers that must agree:

git clone https://github.com/Xaxis/blocklore.space && cd blocklore.space && pnpm install && pnpm verify:snapshot 1
  • Every claim file at the snapshot's commit is hashed again, and the list of ids and hashes must be exactly the snapshot's.
  • The Merkle root over those hashes must be the snapshot's root, and each snapshot must name the previous one's root.
  • The proof must start from the snapshot file's SHA-256 and arrive at the merkle root in the header of the block it names.

With the OpenTimestamps client and a Bitcoin node of your own, the proof checks without any of Blocklore's code:

curl -sO https://blocklore.space/snapshots/1.json -sO https://blocklore.space/snapshots/1.json.ots && ots verify 1.json.ots

Check one claim

Each claim page shows the claim's hash, its place in the newest snapshot and the audit path from its hash to the root. Hash the leaf as SHA-256 of a zero byte followed by the claim's hash, then combine upward: SHA-256 of a one byte, the left hash and the right hash. This is the Merkle tree of RFC 6962, and the path is checked as RFC 9162, section 2.1.3.2 describes; verifyMerkleProof in core/src/hash.ts does exactly that.

What a hash covers

A claim's hash is SHA-256 over its canonical JSON: keys sorted at every level, no spaces, UTF-8, with last_verified left out, so re-checking a claim does not change it. Any change to a statement, a source, a quote, a check or a revision does. The claim format has the whole schema.

What a timestamp proves, and what it does not

  • It proves the snapshot file, and so every claim hash in it, existed before the block was mined. It does not make a claim true: that is what each claim's sources, quotes and checks are for.
  • Snapshots are taken after each publish that changes claims. A claim that changed between two snapshots shows in the first that has its new hash; its revisions keep what it said before, and the publisher refuses rewritten history.
  • Snapshots are not signed yet. The timestamp does not depend on a signature.