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

Card No. 015 · Comfi

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: f2a292b522772d4a8d8ea98a107fb542748499266c4c1dbd66ee0b2377d94c8a
prev: ef13196ee2a9a2800527685681778309c613c7afeace5c21bbec2c39b63428d4
record chain (JSON) · OTS proof (.ots)
Version 3 Bitcoin attested
Recorded July 15, 2026
sha256: ef13196ee2a9a2800527685681778309c613c7afeace5c21bbec2c39b63428d4
prev: 3bd411194f2744f7e8f192525448e99ca745809f099467657f8ff6e9dd747375
record chain (JSON) · OTS proof (.ots)
Version 2 Bitcoin attested
Recorded July 13, 2026
sha256: 3bd411194f2744f7e8f192525448e99ca745809f099467657f8ff6e9dd747375
prev: 94d4448c29b6e26fc75c0cff88d33230cfae551c71d4286f318d17cca9bec912
record chain (JSON) · OTS proof (.ots)
Version 1 Bitcoin attested
Recorded July 4, 2026
sha256: 94d4448c29b6e26fc75c0cff88d33230cfae551c71d4286f318d17cca9bec912
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.