Card No. 002 · Awaiting identity evidence
The founder and the company are named once source evidence admits them; until then the record keeps its number. 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 3
Anchored to Bitcoin
Recorded 18 Jul 2026
sha256: fc4274ceba046a8bc38b4d8c321f8cae1fddf27bcecb9234c03a1a65dbf6f438
prev: 7c36a157804c5734a66c112119341c5ae7f8f4fcbd49b9a0730572f12d7f1b0f
Version 2
Anchored to Bitcoin
Recorded 17 Jul 2026
sha256: 7c36a157804c5734a66c112119341c5ae7f8f4fcbd49b9a0730572f12d7f1b0f
prev: 9d1ba0349a01728cda99ba956a7744b404e362c6179c8284b62c92a0a9246a6a
Version 1
Anchored to Bitcoin
Recorded 17 Jul 2026
sha256: 9d1ba0349a01728cda99ba956a7744b404e362c6179c8284b62c92a0a9246a6a
Verify this yourself
- Download the record chain (JSON). Each entry in versions holds the version's sha256 and its Bitcoin proof. Its text names the founder and the company, so it is published when the identity is admitted, and will hash to these values.
- 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 Delhi 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.