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

Card No. 023 · Record No. 23

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: ef6b3791621d3ff04f382aee3365f65c536cae898505f9f7e868a0b2ad224480
prev: b0c32e217b871571f5caf25728e40ca8eac1be177c8bf0425c4eeb6126487350
record chain (JSON) · OTS proof (.ots)
Version 2 Bitcoin attested
Recorded July 15, 2026
sha256: b0c32e217b871571f5caf25728e40ca8eac1be177c8bf0425c4eeb6126487350
prev: 89b11751599e2ea58bf03e10444c0cff7016d40cd63ac557cd799a780ac94051
record chain (JSON) · OTS proof (.ots)
Version 1 Bitcoin attested
Recorded July 10, 2026
sha256: 89b11751599e2ea58bf03e10444c0cff7016d40cd63ac557cd799a780ac94051
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.