No. 029 · Silkhaus
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: 70b98b278018a7ec72660cf6f7929850851b7f74cd4e71dfc442e43dffb47d77
prev: 884e2a236f197a83e5531821f5d7a81ba5827b9bfa5edd5ae97bae2f9b4f000e
Version 1
Anchored to Bitcoin
Version recorded 10 Jul 2026
sha256: 884e2a236f197a83e5531821f5d7a81ba5827b9bfa5edd5ae97bae2f9b4f000e
Verify this yourself
- Download the record chain (JSON). Each entry in versions holds the record and its sha256.
- Check the chain: every version's prevSha256 must equal the hash of the version before it. A broken link means tampering.
- Compare any hash above against the public ledger. They must match, byte for byte.
- 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