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

Card No. 007 · Fetchr

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 August 9, 2026
sha256: 157fddd2173319ac7cb5f9257741a2fcca43b27e5cb0762afec7766073e41f12
prev: f30dfcc25702c02001e19d3d30dcb5531a44b883f5db80c0f3f3b45b777378c5
record chain (JSON) · OTS proof (.ots)
Version 3 Bitcoin attested
Recorded July 15, 2026
sha256: f30dfcc25702c02001e19d3d30dcb5531a44b883f5db80c0f3f3b45b777378c5
prev: e19c444ed8c6cb93ac6c3ae5bad8437e7213696527d56cd533f0ecb845f17275
record chain (JSON) · OTS proof (.ots)
Version 2 Bitcoin attested
Recorded July 13, 2026
sha256: e19c444ed8c6cb93ac6c3ae5bad8437e7213696527d56cd533f0ecb845f17275
prev: 59b8b3c2d57e579ca4d721069cb5f6045a1f8ba6e65b88c7cdd114a2af69c0a3
record chain (JSON) · OTS proof (.ots)
Version 1 Bitcoin attested
Recorded July 4, 2026
sha256: 59b8b3c2d57e579ca4d721069cb5f6045a1f8ba6e65b88c7cdd114a2af69c0a3
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.