Verify · 検証
A record nobody can quietly edit.
Including us.
Every day at 00:05 UTC, Koryu will publish two files: the board snapshot and the dial snapshot. Before the market has had a chance to grade them, their SHA-256 fingerprints are committed to a public, timestamped log. Later, the files themselves are revealed. Anyone can recompute the hash from the revealed bytes and compare it to the earlier commitment: a match proves the snapshot existed at commitment time and has not been altered since. No trust in us is required at any step, which is the point.
The chain is live: it began with the board's first publication, and every day since is committed and revealed in the public log. Publishing the mechanism first is deliberate. The rules of evidence get fixed before there is any record to flatter, the same pre-registration discipline the research program runs on, covered in the attestation explainer and the verification walkthrough.
The machinery has a production precedent: the Shishin house runs this exact commit-reveal scheme live on its equity record, with a public repository and a standalone verification script, at shishin.io/verify. Koryu inherits the mechanism from day one.
Koryu's ledger is live at the public attestation log. Every attested day is a dated file under reveals/; the earliest is the first attested day, and the repository's standalone verify.py checks any of them.
One honest boundary, stated here the way it is stated everywhere on this site: attestation proves integrity, not quality. It makes the record tamper-evident; it says nothing about whether the measurements are useful. That question belongs to the research, and to you. Decisions are yours.
The four-step check
- Fetch the revealed snapshot for the day you care about.
- Recompute its SHA-256 hash on your own machine.
- Compare it to the hash committed in the public log.
- Check the commitment's timestamp precedes the outcomes you are judging.
Questions
What will Koryu's /verify page prove?
That each day's published board and dial snapshot was committed to at a specific time and has not been edited since. The commitment (a SHA-256 hash) is published before outcomes are knowable; the snapshot bytes are revealed afterward and must match the hash.
Is the attestation live yet?
Yes. The chain began with the board's first daily publication and has recorded every day since. Each day's hash commitment and revealed snapshot sits in the public ledger, checkable with the repository's standalone verify.py.
Does attestation prove the measurements are good?
No. It proves integrity, not quality: the record existed when we say it did and has not changed. Whether the measurements are useful is a separate question the research library addresses, and no attestation can answer it.
Has this mechanism been run in production before?
Yes. The Shishin house, which Koryu is the fifth creature of, runs the same commit-reveal attestation live on its US-equity record, with a public repository and an independent verification script.