No. 004 · CRED
These are dated historical snapshots. The hashes and timestamps establish the contents and timing of each version, not the present truth of its claims. The current record shows separately admitted facts. Original chain and OpenTimestamps files remain available below.
Version 2
Anchored to Bitcoin
Version recorded 18 Jul 2026
sha256: 81e10be637c5d6d8d5ad5f9703b2ef4804acb304bec6023eec6fab4bce7bc7b8
prev: 6b04194e7d3edc367008a2fe93d9a7d34c2eb61c18df7c99890461c43fefeca0
Version 1
Anchored to Bitcoin
Version recorded 17 Jul 2026
sha256: 6b04194e7d3edc367008a2fe93d9a7d34c2eb61c18df7c99890461c43fefeca0
Verify this yourself
- Download the record chain (JSON). Each entry in versions holds the record and its sha256.
- Check the chain: every version's prevSha256 must equal the hash of the version before it. A broken link means tampering.
- Compare any hash above against the public ledger. They must match, byte for byte.
- Drop a version's .ots file and its hash into opentimestamps.org. Bitcoin tells the truth about when that hash existed. No trust in Karnataka of Tomorrow required.
What the states mean: Anchored to Bitcoin · the timestamp is confirmed in a Bitcoin block. Timestamping in progress · the hash is submitted to OpenTimestamps and awaits its Bitcoin block, dated from the day it was submitted; until then, git history is the backstop. Recorded · the version is on the record and not yet submitted.