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

Card No. 029 · Record No. 29

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