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

Card No. 032 · Tarabut

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 17, 2026
sha256: a8feef946d90b50fbe00440227a61c8203d13ff8add24c8535a633533ffc3453
prev: c49c7e52ca6597d8e49bc29feb869227676a3bc716d3f7da419f4a219b83404a
record chain (JSON) · OTS proof (.ots)
Version 3 Bitcoin attested
Recorded July 16, 2026
sha256: c49c7e52ca6597d8e49bc29feb869227676a3bc716d3f7da419f4a219b83404a
prev: ab848a776309df6dc730b7e845801d2589a0565e18f0b61d4d1efcab39381336
record chain (JSON) · OTS proof (.ots)
Version 2 Bitcoin attested
Recorded July 15, 2026
sha256: ab848a776309df6dc730b7e845801d2589a0565e18f0b61d4d1efcab39381336
prev: dc9d76877b179bece97936cb0e1f0a8cb47edf36df19bbe4b66da291601d6b16
record chain (JSON) · OTS proof (.ots)
Version 1 Bitcoin attested
Recorded July 10, 2026
sha256: dc9d76877b179bece97936cb0e1f0a8cb47edf36df19bbe4b66da291601d6b16
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.