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

Card No. 008 · Careem

Founder profiles are living documents. When the story evolves, a new version of this record is created and anchored. Nothing is rewritten silently: every version below is hashed, linked to the one before it, and timestamped on Bitcoin via OpenTimestamps. This is the Anchored Record Protocol, applied to one card.

Version 4 Bitcoin attested
Recorded July 16, 2026
sha256: 2d3334c2a8e041ba0c5be2091ee15668d1a0f8490345de41b7b44fa395dfa17f
prev: 81c11f34907998d0f278e00074f08ac6f5eea7508ac1c159686f6258f3d2e3cf
record chain (JSON) · OTS proof (.ots)
Version 3 Bitcoin attested
Recorded July 15, 2026
sha256: 81c11f34907998d0f278e00074f08ac6f5eea7508ac1c159686f6258f3d2e3cf
prev: 664f9b7d54ca7c900bc660fd30aed3f36b70849e296b804f1685fae0a33cbf77
record chain (JSON) · OTS proof (.ots)
Version 2 Bitcoin attested
Recorded July 13, 2026
sha256: 664f9b7d54ca7c900bc660fd30aed3f36b70849e296b804f1685fae0a33cbf77
prev: 250ed1fa1fcdf26851c304936481850fc1e6145f8e555294cbbbcab67e5d16c7
record chain (JSON) · OTS proof (.ots)
Version 1 Bitcoin attested
Recorded July 4, 2026
sha256: 250ed1fa1fcdf26851c304936481850fc1e6145f8e555294cbbbcab67e5d16c7
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.