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

Card No. 018 · Alaan

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 Anchored to Bitcoin
Recorded 16 Jul 2026
sha256: e009e47c682a8743835ed43fd5bf87b0ed6e80d39395f237a905df577bf29896
prev: fa6f479fb154ac694e3cc44561280356c18d742ebe60982ab1670ed4ad5467d2
record chain (JSON) · OTS proof (.ots)
Version 2 Anchored to Bitcoin
Recorded 15 Jul 2026
sha256: fa6f479fb154ac694e3cc44561280356c18d742ebe60982ab1670ed4ad5467d2
prev: 011bdc78438b3221afba7fe31c33dd6342bab792741a3486c4a4543fede19445
record chain (JSON) · OTS proof (.ots)
Version 1 Anchored to Bitcoin
Recorded 10 Jul 2026
sha256: 011bdc78438b3221afba7fe31c33dd6342bab792741a3486c4a4543fede19445
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 states mean: Anchored to Bitcoin · the timestamp is confirmed in a Bitcoin block. Timestamping in progress · the hash is submitted to OpenTimestamps and awaits its Bitcoin block, dated from the day it was submitted; until then, git history is the backstop. Recorded · the version is on the record and not yet submitted.