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

Card No. 044 · Record No. 44

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 4 Bitcoin attested
Recorded August 9, 2026
sha256: ffa9f6672b689ca988377c24a19f05ba846910aa0b5bc155f9cad75f2ec2a8a3
prev: 04a0951209318193b07de2b9789bd0f8e3100d8825006f59d11b6805b69bd199
record chain (JSON) · OTS proof (.ots)
Version 3 Bitcoin attested
Recorded July 17, 2026
sha256: 04a0951209318193b07de2b9789bd0f8e3100d8825006f59d11b6805b69bd199
prev: b2785e8f32586156989ca070c977334f7b700bec481cbec8472d9d994b32b5ba
record chain (JSON) · OTS proof (.ots)
Version 2 Bitcoin attested
Recorded July 15, 2026
sha256: b2785e8f32586156989ca070c977334f7b700bec481cbec8472d9d994b32b5ba
prev: 8e403316e256b5a6a1c4dfd373fa9f89c05ae7bb62427ada07780ec0cafedbf5
record chain (JSON) · OTS proof (.ots)
Version 1 Bitcoin attested
Recorded July 10, 2026
sha256: 8e403316e256b5a6a1c4dfd373fa9f89c05ae7bb62427ada07780ec0cafedbf5
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.