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

Card No. 030 · Record No. 30

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: 3c741bd24b8df8c015151b3a1d5316e8af0a8c29c03d7693202958f29ced5c18
prev: dc779b4549847e84e70924e2b7949b3c3139e45d6a21aaf1928a112a78e0c778
record chain (JSON) · OTS proof (.ots)
Version 3 Bitcoin attested
Recorded July 16, 2026
sha256: dc779b4549847e84e70924e2b7949b3c3139e45d6a21aaf1928a112a78e0c778
prev: c78c1857bee3ebe5e37cb09227b7b8d22c610735dcdcaf87a01244fe808c0e79
record chain (JSON) · OTS proof (.ots)
Version 2 Bitcoin attested
Recorded July 15, 2026
sha256: c78c1857bee3ebe5e37cb09227b7b8d22c610735dcdcaf87a01244fe808c0e79
prev: df4d7efc73523542715982845421c39b4d692208f0ec13a9a5ce3af96222c313
record chain (JSON) · OTS proof (.ots)
Version 1 Bitcoin attested
Recorded July 10, 2026
sha256: df4d7efc73523542715982845421c39b4d692208f0ec13a9a5ce3af96222c313
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.