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

Card No. 033 · Careem

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 3 Bitcoin attested
Recorded July 17, 2026
sha256: 15f1d70e7c4a8c3baa1274c8384688d7bc4c5d15d45ab79179778b6b0a1152c7
prev: 5c4688aa2b2fd805449729abf52d631083bd15e27905ae9621da605ab9ed81bd
record chain (JSON) · OTS proof (.ots)
Version 2 Bitcoin attested
Recorded July 15, 2026
sha256: 5c4688aa2b2fd805449729abf52d631083bd15e27905ae9621da605ab9ed81bd
prev: 887c1f31f2a45d5ab84b04ed1f279707dd72aba81cc78f7a8a0e2024974313eb
record chain (JSON) · OTS proof (.ots)
Version 1 Bitcoin attested
Recorded July 10, 2026
sha256: 887c1f31f2a45d5ab84b04ed1f279707dd72aba81cc78f7a8a0e2024974313eb
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.