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

Card No. 045 · Verity

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 July 17, 2026
sha256: 1d9e6e6fd1c1e06fd2bc486d5cb9a2baeca12437758f374ad9739504e9780b62
prev: 6492326e2f636ac10c86835e8a77496a9e39476cc3182a7aa05efaa27f09974f
record chain (JSON) · OTS proof (.ots)
Version 3 Bitcoin attested
Recorded July 16, 2026
sha256: 6492326e2f636ac10c86835e8a77496a9e39476cc3182a7aa05efaa27f09974f
prev: aa44ec75772b015c69067b671c5b66604f0967285e970c44b629e86849b293a5
record chain (JSON) · OTS proof (.ots)
Version 2 Bitcoin attested
Recorded July 15, 2026
sha256: aa44ec75772b015c69067b671c5b66604f0967285e970c44b629e86849b293a5
prev: c37d674250d5c2dcb835b87ba3ad5fe7991b3dfe3eaf0245705131443313e6a2
record chain (JSON) · OTS proof (.ots)
Version 1 Bitcoin attested
Recorded July 10, 2026
sha256: c37d674250d5c2dcb835b87ba3ad5fe7991b3dfe3eaf0245705131443313e6a2
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.