Evidence and sources
The four resolver lanes, linked evidence and the difference between recording evidence and verifying an off-chain fact.
Read the rules before trading#
The template fixes the outcomes, source policy, timing and resolution lane. Check the market's resolution panel and evidence links. A source can become unavailable or disputed; template validation cannot guarantee the truth of an off-chain report.
Four implemented lanes#
| Lane | Who reports | Authority |
|---|---|---|
| Chain read | Anyone invoking the configured reporter | Supported on-chain observation |
| Attested | Anyone presenting the required registered signatures | Signer quorum |
| Optimistic | Bonded proposers and challengers, with a court after escalation | Public challenge process and final court |
| Committee | The configured committee address | Committee decision |
The lane's published timer is metadata, not a universal extra delay after a valid report. Enforced waiting periods are specific to each resolver. In particular, the attested lane has an evidence commit delay but no optimistic challenge round.
Evidence records#
Evidence records contain a content hash, URI and fetch time, and are linked to a condition. The router requires linked evidence before accepting a report. Records are append-only. Anyone may commit evidence; a commitment proves which bytes were referenced, not that the claim is true.
Chain-read evidence is generated during observation. Attested evidence must be committed at least one hour before submission. Optimistic proposals and challenges reference linked evidence; committee reports do too.
Source support#
The chain reporter's configured catalogue determines which contract reads it can perform. A market cannot add an arbitrary call. Off-chain categories need reviewed templates, evidence sources and reporting operators. See Template permissions.