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

Card No. 037 · Record No. 37

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 4 Bitcoin attested
Recorded August 9, 2026
sha256: d0c852f3ebe42aceb3cf7b4e5e33330ebd6588df051dbb75ef2d8a047c730693
prev: b0a7e46bec73dacf9db9d910185cbe639adfc5699d6a4740c51ddff7a550e638
record chain (JSON) · OTS proof (.ots)
Version 3 Bitcoin attested
Recorded July 16, 2026
sha256: b0a7e46bec73dacf9db9d910185cbe639adfc5699d6a4740c51ddff7a550e638
prev: 21497039371f36f9b08916e6649c9375765cd562fe71f6c451eabcb6729da5c3
record chain (JSON) · OTS proof (.ots)
Version 2 Bitcoin attested
Recorded July 15, 2026
sha256: 21497039371f36f9b08916e6649c9375765cd562fe71f6c451eabcb6729da5c3
prev: 2684f28d9305280ff56dbb2a77507a67d3512b1cbd3c73c6ee4894d491527738
record chain (JSON) · OTS proof (.ots)
Version 1 Bitcoin attested
Recorded July 10, 2026
sha256: 2684f28d9305280ff56dbb2a77507a67d3512b1cbd3c73c6ee4894d491527738
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.