Card No. 001 · 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 2
Anchored to Bitcoin
Recorded 18 Jul 2026
sha256: cdb55a60d9d1527694fbad00f6c20f40cc58997f5dea5d657290d77e790ec7a8
prev: 0ba5730e9538797a1af54b0d93e7844ab0ab6d639bd40f1ca4ae6813ec428f3e
Version 1
Anchored to Bitcoin
Recorded 17 Jul 2026
sha256: 0ba5730e9538797a1af54b0d93e7844ab0ab6d639bd40f1ca4ae6813ec428f3e
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.