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

Card No. 021 · Swvl

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: 04dd8595ba8a8c2097765a06450522dd975d5e4e923b91336f1196e93203ca38
prev: a2b57fcdbb594e2b38b1768f1f15e829f3a92e9a8f760d607f8a1c3a07feedfc
record chain (JSON) · OTS proof (.ots)
Version 3 Bitcoin attested
Recorded July 16, 2026
sha256: a2b57fcdbb594e2b38b1768f1f15e829f3a92e9a8f760d607f8a1c3a07feedfc
prev: 97eddf5e47cb08a0d18eec3ca1347025acd676357b96a6d1368398cbaddabd5f
record chain (JSON) · OTS proof (.ots)
Version 2 Bitcoin attested
Recorded July 15, 2026
sha256: 97eddf5e47cb08a0d18eec3ca1347025acd676357b96a6d1368398cbaddabd5f
prev: c0f76c5751e582c03d7759c4db020524fe299b31363c2b8f33a1c1e4f2869c01
record chain (JSON) · OTS proof (.ots)
Version 1 Bitcoin attested
Recorded July 10, 2026
sha256: c0f76c5751e582c03d7759c4db020524fe299b31363c2b8f33a1c1e4f2869c01
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.