VERIFICATION · BUILT TO BE AUDITED

Verify the record, not the prediction.

Verification checks that the position shown today is the same record GLINTARY locked before the event. It does not prove the pick was correct.

5 commitments on record

VERIFICATION RESULT

All checks passed. The published record matches its commitment.

VerifiedPosition GL-20260906-006

Record status: REVEALED
Checks: 5 of 5 passed
Committed: 2026-09-06 07:58 UTC
Timestamp proof: COMMITTED

Position IDGL-20260906-006

Record fingerprint20daa2a484bd878623b8ee67a74228edde2b012b2207ff23acec8eaa0a227593

Checks that were run5 of 5 passed · Merkle root and batch

PASScanonical_formPayload is in RFC 8785 canonical form.
PASSposition_idPayload names GL-20260906-006.
PASSrecorded_oddsRecorded price 3.150 matches the payload.
PASSleaf_hashSHA-256(0x00 || payload) reproduces the committed leaf.
PASSinclusionAudit path reproduces the published Merkle root.

Merkle root · batch BOARD-20260906-D2b93200df73cb54ce430c365f1993e412255da14676e52b37e986c6502c1bc84

Open the batch

Back to the position

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.

How a record is verified

Lock
At lock time, GLINTARY creates a cryptographic fingerprint of the exact position record.
Commit & timestamp
A commitment to that fingerprint is published with a public timestamp reference.
Verify
Anyone can later check that the published record still matches the original commitment.

Commitments on record

BOARD-20260906-D
COMMITTED
Records
1
Committed
2026-09-06 07:58 UTC
BOARD-20260906-C
COMMITTED
Records
1
Committed
2026-09-06 06:42 UTC
BOARD-20260906-B
COMMITTED
Records
2
Committed
2026-09-06 06:17 UTC
BOARD-20260906-A
COMMITTED
Records
1
Committed
2026-09-06 04:10 UTC
BOARD-20260904-A
COMMITTED
Records
1
Committed
2026-09-04 01:55 UTC

How a commitment is builtCanonical JSON, SHA-256, Merkle tree, timestamp anchors

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.

Batch	Root fingerprint	Records	Created	Timestamp proof
BOARD-20260906-D	2b93200df73cb54c…	1	2026-09-06 07:58 UTC	COMMITTED
BOARD-20260906-C	875ce1dfa5e04511…	1	2026-09-06 06:42 UTC	COMMITTED
BOARD-20260906-B	eebd80a33def89bd…	2	2026-09-06 06:17 UTC	COMMITTED
BOARD-20260906-A	78fc311552a5ffdc…	1	2026-09-06 04:10 UTC	COMMITTED
BOARD-20260904-A	bfbcc89c3613568d…	1	2026-09-04 01:55 UTC	COMMITTED

All checks passed. The published record matches its commitment.

How a record is verified

Lock

Commit & timestamp

Verify

Commitments on record

BOARD-20260906-D

BOARD-20260906-C

BOARD-20260906-B

BOARD-20260906-A

BOARD-20260904-A