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

Card No. 006 · TruDoc

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: 2bd65324afc80bd27edd263cf506e958987864cf4e45287e5a1d09d41e140722
prev: 9d58675a2e38e8c247cd0eadf7714cec7ceb86ad0b8e17744b82df90bbefdbf5
record chain (JSON) · OTS proof (.ots)
Version 3 Bitcoin attested
Recorded July 15, 2026
sha256: 9d58675a2e38e8c247cd0eadf7714cec7ceb86ad0b8e17744b82df90bbefdbf5
prev: 80edbdb35f803027268bfcb6e873f201a6fb9862e5703b618af02b6b2432d820
record chain (JSON) · OTS proof (.ots)
Version 2 Bitcoin attested
Recorded July 13, 2026
sha256: 80edbdb35f803027268bfcb6e873f201a6fb9862e5703b618af02b6b2432d820
prev: 7c1ccae22d6684144ae512a054cd77b7a316bcf05c9b8c7c9418038c320cbc8e
record chain (JSON) · OTS proof (.ots)
Version 1 Bitcoin attested
Recorded July 4, 2026
sha256: 7c1ccae22d6684144ae512a054cd77b7a316bcf05c9b8c7c9418038c320cbc8e
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.