GLINTARY
Morning Brief
GLINTARY
Morning Brief

RECORD INTEGRITY

Proof that a published position was not changed later.

Official positions can be tied to a timestamped cryptographic commitment.

  1. 1

    Lock

    At lock time, GLINTARY creates a cryptographic fingerprint of the exact position record.

  2. 2

    Timestamp

    A commitment to that fingerprint is published with a public timestamp reference.

  3. 3

    Verify

    Anyone can later check that the published record still matches the original commitment.

Verification proves record integrity and timing. It does not prove that a position was correct or that the quoted odds were available to every user.

Odds evidence is recorded separately with the source, region, odds and observation time.

A hash is a one-way digital fingerprint of the exact record. If the record changes, the fingerprint changes.

Commitments on record

Verification will activate with the first cryptographically committed position.

Technical details

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.