Saudi of Tomorrow
← Back to the record
Saudi of Tomorrow · Proof of record

Card No. 001 · Record No. 1

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 3 Bitcoin attested
Recorded 16 Jul 2026
sha256: 14e310d389e2d66193e81d258397b580076e1d0a238a575160dbbc2d76ef8334
prev: 8cf20a47d254dfcaac06b60c64b303181209d94196ea5f81c0a2c646663677b1
record chain (JSON) · OTS proof (.ots)
Version 2 Bitcoin attested
Recorded 15 Jul 2026
sha256: 8cf20a47d254dfcaac06b60c64b303181209d94196ea5f81c0a2c646663677b1
prev: 7b145691811786ca7c99aff5c942c5283ada9afd931f499a63a57b0ba0dd75ee
record chain (JSON) · OTS proof (.ots)
Version 1 Bitcoin attested
Recorded 4 Jul 2026
sha256: 7b145691811786ca7c99aff5c942c5283ada9afd931f499a63a57b0ba0dd75ee
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 Saudi 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.