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

Card No. 020 · Kitopi

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: ec43041c004ef66e7656ef4bf1837008636ba414ec793b619a4da4160504ed5e
prev: 8dd9f3de4eef2a77384f664e50028e6070d900640576f9b9dcbfc64363db8b7d
record chain (JSON) · OTS proof (.ots)
Version 3 Bitcoin attested
Recorded July 17, 2026
sha256: 8dd9f3de4eef2a77384f664e50028e6070d900640576f9b9dcbfc64363db8b7d
prev: 518a7bafa38d4e3822fd311dab0e569b49893e68a2e23b42a2bb7194340d4a68
record chain (JSON) · OTS proof (.ots)
Version 2 Bitcoin attested
Recorded July 15, 2026
sha256: 518a7bafa38d4e3822fd311dab0e569b49893e68a2e23b42a2bb7194340d4a68
prev: 4a62b509752487441720744efff16de4d9524ed23f1cf013a014f2ca27308bc9
record chain (JSON) · OTS proof (.ots)
Version 1 Bitcoin attested
Recorded July 10, 2026
sha256: 4a62b509752487441720744efff16de4d9524ed23f1cf013a014f2ca27308bc9
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.