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

No. 038 · Okadoc

These are dated historical snapshots. The hashes and timestamps establish the contents and timing of each version, not the present truth of its claims. The current record shows separately admitted facts. Original chain and OpenTimestamps files remain available below.

Version 2 Anchored to Bitcoin
Version recorded 15 Jul 2026
sha256: 0f58265c294c5e5b6593074783a2bec359ddda78016a871727fdf2239651c109
prev: 1210bd855f1dc2950dc6886755f43cc5ab3959826346e4c7819c80272c6d0f62
record chain (JSON) · OTS proof (.ots)
Version 1 Anchored to Bitcoin
Version recorded 10 Jul 2026
sha256: 1210bd855f1dc2950dc6886755f43cc5ab3959826346e4c7819c80272c6d0f62
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. Give a version's .ots file and its hash to opentimestamps.org: drop the file on that page, or on a phone choose it from the downloads. Bitcoin tells the truth about when that hash existed. No trust in Dubai of Tomorrow required.

What the states mean: Anchored to Bitcoin · the timestamp is confirmed in a Bitcoin block. Timestamping in progress · the hash is submitted to OpenTimestamps and awaits its Bitcoin block, dated from the day it was submitted; until then, git history is the backstop. Recorded · the version is on the record and not yet submitted.

© 2026 Proptefi Tech Limited · Published by Proptefi