Why are the source, initial report, and final result different things?
How Does a Chain Know What Happened in Reality?
Start with a potentially wrong report and see why an oracle is more than an API—and why price cannot repair a bad fact.
We break the gap between the chain and the outside world into sources, reports, challenge windows, and arbitration so every trust assumption has a state and a cost.
- SRCSource: provide an observation from outside the chain
- REPReporter: submit a result with a bond
- CHLChallenger: risk a bond to contest the report
- ARBArbitrator: read evidence and decide payout
One question per lesson
The lessons are ordered so that each one uses concepts introduced earlier.
- 01REPORT · CHALLENGE · FINALIZE12 MIN
Code Cannot See Outside the Window
KEY QUESTIONWhy can an honest oracle reporter still be wrong?
Let a reporter, challenger, and arbitrator complete one round of bringing a real-world result onchain.
→ - 02SOURCE · EVIDENCE · REPORT13 MIN
Why Is One API Result Not Enough?
KEY QUESTIONWhy aren’t ten APIs necessarily more decentralized than one?
Switch between reliable, conflicting, and ambiguous sources to separate data quality, reporters, and real-world evidence.
→ - 03CHALLENGE · BOND · ARBITRATION14 MIN
Why Give a Wrong Report a Rebuttal Window?
KEY QUESTIONIs a larger oracle bond always safer?
Lock opposite outcomes and watch time and economic loss create room for correction.
→ - 04FINALIZE · HANDOFF · FAILURE13 MIN
How Does a Final Result Reach the Market Safely?
KEY QUESTIONWhy doesn’t FINAL mean absolutely true?
Hand a final result to a prediction market and compare correct reports, unchallenged errors, and dispute correction.
→
Questions covered in this course
How does a challenge window leave time to correct a wrong report?
How does an economic bond turn being wrong into a real loss?
Why can an unchallenged wrong report still settle a market, and how should handoff be audited?