← Back to the record
Delhi of Tomorrow · Proof of record

Card No. 003 · Policybazaar

Founder profiles are living documents. When the story evolves, a new version of this record is created and anchored. Nothing is rewritten silently: every version below is hashed, linked to the one before it, and timestamped on Bitcoin via OpenTimestamps. This is the Anchored Record Protocol, applied to one card.

Version 3 Bitcoin attested
Recorded July 18, 2026
sha256: 39af4598b0e6ad8498245d119e3997d38326293d96c2a82af60acff6e953b2b6
prev: 014af203cb117756fa62ec0d4d760c6a42d97258709c2b55eeea8ec3d68319b7
record chain (JSON) · OTS proof (.ots)
Version 2 Bitcoin attested
Recorded July 17, 2026
sha256: 014af203cb117756fa62ec0d4d760c6a42d97258709c2b55eeea8ec3d68319b7
prev: 4adcf5b29be2b33d285ed575bbb14edbc11f2211dd440e44b6f52feb2df24c5a
record chain (JSON) · OTS proof (.ots)
Version 1 Bitcoin attested
Recorded July 17, 2026
sha256: 4adcf5b29be2b33d285ed575bbb14edbc11f2211dd440e44b6f52feb2df24c5a
record chain (JSON) · OTS proof (.ots)
Verify this yourself
  1. Download the record chain (JSON). Each entry in versions holds the record and its sha256.
  2. Check the chain: every version's prevSha256 must equal the hash of the version before it. A broken link means tampering.
  3. Compare any hash above against the public ledger. They must match, byte for byte.
  4. 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 statuses mean: Bitcoin attested · the timestamp is confirmed in a Bitcoin block. Attestation pending · the hash is anchored with OpenTimestamps and awaiting Bitcoin confirmation, usually within hours; until then, git history is the backstop.