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

Card No. 028 · Record No. 28

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: 18d329b02c66fa00b2aef41bf7067b170c8630b53712eb843a8edcebd5f4976f
prev: 338ab154269d8e69294422b2db65d5e64ba8685a4d7fc997f37e140fe7d6c0e2
record chain (JSON) · OTS proof (.ots)
Version 2 Bitcoin attested
Recorded July 15, 2026
sha256: 338ab154269d8e69294422b2db65d5e64ba8685a4d7fc997f37e140fe7d6c0e2
prev: 3a8467b1fca21b60072e4b4c92de8e02ad9f563018ba24ba456d63d159ff4655
record chain (JSON) · OTS proof (.ots)
Version 1 Bitcoin attested
Recorded July 10, 2026
sha256: 3a8467b1fca21b60072e4b4c92de8e02ad9f563018ba24ba456d63d159ff4655
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.