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

Card No. 034 · Record No. 34

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 August 9, 2026
sha256: 1bff3f8d2a896bff30d98d02f2643d5eb741cb7b11cf1d49541d163e919e4da3
prev: ef48ce418fc4bfcf111f2b5ba41f14dfb001912c69376739460a07835be0df0a
record chain (JSON) · OTS proof (.ots)
Version 2 Bitcoin attested
Recorded July 15, 2026
sha256: ef48ce418fc4bfcf111f2b5ba41f14dfb001912c69376739460a07835be0df0a
prev: 90cd62e7750483ba2afab548a42cbdd830487c07ef2aad0c4f7b5b4c859b97d9
record chain (JSON) · OTS proof (.ots)
Version 1 Bitcoin attested
Recorded July 10, 2026
sha256: 90cd62e7750483ba2afab548a42cbdd830487c07ef2aad0c4f7b5b4c859b97d9
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.