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

Card No. 025 · Record No. 25

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 Bitcoin attested
Recorded July 17, 2026
sha256: 94960b0b6d09d22014a4087dc95c55746d1c3b0d245ffb17ee2285360dc440ca
prev: be1ca3bbf1968201ba3987ae821702d6540c67600cdbfed3a42d139bdccfb780
record chain (JSON) · OTS proof (.ots)
Version 2 Bitcoin attested
Recorded July 15, 2026
sha256: be1ca3bbf1968201ba3987ae821702d6540c67600cdbfed3a42d139bdccfb780
prev: 1b31e94cca9e8f94f18e2d32a0e463183029fea553710a81ebfd207cc39c896d
record chain (JSON) · OTS proof (.ots)
Version 1 Bitcoin attested
Recorded July 10, 2026
sha256: 1b31e94cca9e8f94f18e2d32a0e463183029fea553710a81ebfd207cc39c896d
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 Dubai 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.