Public registry
Every hour,a fingerprint in Bitcoin
Here is the fingerprint of everything OX212 seals: receipts, readings and predictions. It carries none of your data, and anyone can verify it independently
- Seals
- —
- Checked
- —
- Latest seal
- —
- In Bitcoin
- —
Every hour, if there is something new to seal. Bitcoin takes between 1 and 6 hours to confirm each seal: until then, it shows as awaiting a block.
What gets sealed
What OX212 puts on record, and when
- 01
What it saw coming
Each day's reading and every prediction, sealed with its time before it happens. Nobody can claim afterwards that they knew all along.
- 02
What it did
Every warning and every pause, with its reason and its time. And every pause leaves its own receipt, as if before a notary.
- 03
How it ended
Whether the prediction came true or not, and what happened after the pause. That's how we measure whether OX212 gets it right, with no way to touch anything up.
For you, it's independently verifiable proof. If your funded firm asks what happened on an account, or you want to show your discipline with the Passport, it's there, with date and time. Your data never leaves OX212: only a fingerprint goes to Bitcoin.
The registry, live
Every seal
Loading the registry…
Check it yourself
Verify it in one click
Your browser downloads the latest anchored seal’s document and proof, computes its fingerprint and follows it to its Bitcoin block, which it reads from a public explorer. If anyone had touched anything, it would not match.
Or outside OX212, in three steps
- 01
Download
A seal’s document and one of its .ots proofs, into the same folder.
- 02
Open them
At opentimestamps.org, the open protocol’s site, with nothing to install. If you run a Bitcoin node, with its client too, as below.
- 03
Verify
Bitcoin confirms which block holds it and since when that seal exists.
pip install opentimestamps-client ots verify ox212-seal-1.json.ots Success! Bitcoin block … attests existence as of …
The rules, in the open
How each fingerprint is computed
For anyone who wants to redo the math: this is how the leaves, each hour’s tree and the chain that links a seal to the last one are built.
leaf = sha256(salt || sha256(content))node = sha256(0x01 || left || right)chain = sha256(prev_chain || root)Copy on GitHubA public copy updated with every seal and never overwrittenThere is no trader data here, only salted fingerprints. If someone deletes their account, their salt is deleted, and their fingerprint no longer leads to anyone.


