This page runs the platform's own checks against the platform, live, with no login. For each market it rehashes the question to prove the terms weren't reworded, compares the outcome the ledger paid on against the outcome recorded on chain, and replays the settlement maths over the stored stakes to see whether it reproduces the published receipt. It then recomputes every hash link in the transaction log, and checks that every point in existence traces back to a grant, a position or a payout. A red result below is a real finding, not a rendering bug.

All the points on a market form one pool. When it resolves, the pool is shared among the correct forecasts in proportion to what each committed. The arithmetic rules below are the ones every settlement on this page is re-derived with.

An outcome becomes payable only when signers from enough independent organisations agree, and only after a challenge window that opens once they do. Signers from the same organisation count once. The one way around this is an operator override, which every market it touches shows as unattested.

Append-only and hash-linked: each entry's hash is computed over the entry before it, so editing any past record breaks every hash that follows. createMarket commits a market's terms, setOutcome records the resolved result and who attested to it, and recordSettlement commits the Merkle root of the payout table.

The log above is kept on Veridix's own server. Hash links show tampering by anyone else, but an operator could rewrite a record and recompute every hash after it. So checkpoints of the log's latest hash are timestamped by OpenTimestamps, which anchors them in Bitcoin. To check one yourself, download its statement and proof, run ots upgrade then ots verify on the proof, and compare the hash in the statement with the log at that height.