Loading verification…
Loading verification…
VERIFICATION · BUILT TO BE AUDITED
Verification checks that the position shown today is the same record GLINTARY locked before the event. It does not prove the pick was correct.
VERIFICATION RESULT
VerifiedPosition GL-20260906-002
GL-20260906-002c3afd352f0f82295f9fc2fa9fc11c7bb4d5cd4df0a9bd9ceff69573a7616c69178fc311552a5ffdc827b79f9b0a0419f77def3cfba9a9343470347ec9f18b12aAt lock time, GLINTARY creates a cryptographic fingerprint of the exact position record.
A commitment to that fingerprint is published with a public timestamp reference.
Anyone can later check that the published record still matches the original commitment.
| Batch | Root fingerprint | Records | Created | Timestamp proof |
|---|---|---|---|---|
| BOARD-20260906-D | 2b93200df73cb54c… | 1 | COMMITTED | |
| BOARD-20260906-C | 875ce1dfa5e04511… | 1 | COMMITTED | |
| BOARD-20260906-B | eebd80a33def89bd… | 2 | COMMITTED | |
| BOARD-20260906-A | 78fc311552a5ffdc… | 1 | COMMITTED | |
| BOARD-20260904-A | bfbcc89c3613568d… | 1 | COMMITTED |
The canonical position record (RFC 8785 canonical JSON) is hashed with SHA-256 together with a random nonce. The hashes of a day's positions form the leaves of a Merkle tree (RFC 6962 domain separation: 0x00 for leaves, 0x01 for interior nodes). Only the root is published as the commitment.
The root can be anchored with an RFC 3161 timestamp token, an OpenTimestamps proof, or a public post. Verification recomputes the leaf from the published record and nonce, follows the inclusion path and compares the result with the committed root.
The website production lock is the start of the cryptographic production record. No commitment is created retrospectively for research published before launch.