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

Card No. 026 · Record No. 26

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: 80933ce906fb58ebc9f6312fd521e751c51df31cb2d052dfd08ee84b7f22f597
prev: d3e2b25be0db4e06d47a45f0a51a916ab83ee6e255794406922347a42f640207
record chain (JSON) · OTS proof (.ots)
Version 3 Bitcoin attested
Recorded July 17, 2026
sha256: d3e2b25be0db4e06d47a45f0a51a916ab83ee6e255794406922347a42f640207
prev: 05fdefe90b52a34a9143bb04084136e8557cee2f480c74b63b35865f645f284d
record chain (JSON) · OTS proof (.ots)
Version 2 Bitcoin attested
Recorded July 15, 2026
sha256: 05fdefe90b52a34a9143bb04084136e8557cee2f480c74b63b35865f645f284d
prev: 2212ddb3adb445a2da5990522fefb1f6486227a7124c32f71fcc29d2097010f1
record chain (JSON) · OTS proof (.ots)
Version 1 Bitcoin attested
Recorded July 10, 2026
sha256: 2212ddb3adb445a2da5990522fefb1f6486227a7124c32f71fcc29d2097010f1
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.