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

Card No. 024 · Fuze

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: a2096c0089169760a04fe3e94c9f834575c1eb27e7a0ee3b318572010fbdb0f2
prev: 30d727ff77f45a53f5bfc78c222b0f564c3c86ea2ce4373062b8629b0c694069
record chain (JSON) · OTS proof (.ots)
Version 3 Bitcoin attested
Recorded July 16, 2026
sha256: 30d727ff77f45a53f5bfc78c222b0f564c3c86ea2ce4373062b8629b0c694069
prev: 419ff6ad2b4558f4354195be0a4e9f8817d33454b65069f5c58bd39222940e10
record chain (JSON) · OTS proof (.ots)
Version 2 Bitcoin attested
Recorded July 15, 2026
sha256: 419ff6ad2b4558f4354195be0a4e9f8817d33454b65069f5c58bd39222940e10
prev: 3f9ccee8235357c48ce4f0219b4b043949ec9437ac077084fbaf9ea2350aed7b
record chain (JSON) · OTS proof (.ots)
Version 1 Bitcoin attested
Recorded July 10, 2026
sha256: 3f9ccee8235357c48ce4f0219b4b043949ec9437ac077084fbaf9ea2350aed7b
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.