clause.

Were we right before?

Verdicts published before the contracts resolve, scored after. Refutations are listed. A scorecard showing only hits is marketing.

loading

Read published and days_of_record before reading accuracy. A handful of decided pairs is not a track record, and we would rather say so than let a number imply otherwise.

What is being recorded, and why it is hard to fake

The archive

Terms, as they stood that day

Venues edit resolution criteria in place. A contract you read in March can settle in June on wording that changed in April, and the old text is simply gone.

So the terms are snapshotted daily and hash-chained: each day's record commits to the one before it, which makes a silent edit to the history detectable rather than merely unlikely.

A missed day cannot be backfilled. It is the one asset here that only accrues.

The scoring

Published first, scored later

A verdict counts only if it was recorded before the contract resolved. Anything scored after the fact is a story, not a record.

/v1/evidence returns a bundle that reproduces a verdict from the archived inputs, and /v1/evidence/verify checks one you were handed earlier — including one that disagrees with what we would say today.

This page is one call to /v1/scorecard. Read the API →