reality.eth

  • Name: reality.eth
  • URL: https://reality.eth.limo/
  • Category: subjective oracle / optimistic-dispute primitive / arbitration-dependent governance-execution infrastructure
  • Summary: reality.eth is best understood as an optimistic truth-adjudication primitive rather than as a generic oracle feed. It lets anyone ask arbitrary questions onchain, uses escalating answer bonds to make false claims expensive, and delegates hard edge cases to a pluggable arbitrator contract. The reusable governance insight is that when protocols rely on reality.eth, the real control surface is not only the bond game; it is the combination of question templating, timeout design, and arbitrator selection that determines how disputed offchain facts become executable onchain outcomes.
  • What it does:
    • Lets users or contracts ask arbitrary structured questions and receive an answer after a timeout period
    • Uses an escalating bond game where each new answer must at least double the previous bond, resetting the clock and making disputes progressively more expensive
    • Supports commit-reveal answering to reduce front-running by letting answerers commit a hash before revealing the answer
    • Allows any contract address to serve as arbitrator, so downstream systems can plug in centralized, jury-style, stakeholder-voting, or other dispute-resolution models
    • Ships a full public stack including contracts, question/template libraries, dapp, docs, CLI tools for arbitration, and subgraph definitions
  • Key claims:
    • The official docs describe reality.eth as a “crowd-sourced on-chain smart contract oracle system” that can be used from its web app or directly from contracts
    • The whitepaper says the system’s goals are to let arbitrary questions be asked, reward right answers, penalize wrong answers, keep typical resolution cheap, and make resource-intensive dispute resolution possible when needed
    • The same whitepaper describes the core mechanism as an answer-bond escalation game where each new answer must post at least double the previous bond and can be finalized after a timeout unless arbitration is requested
    • The docs say commit-reveal answers exist specifically to mitigate transaction front-running, which matters because the primitive depends on being first with correct information
    • The arbitrators documentation says any contract address can be used as arbitrator and explicitly lists trusted third parties, jury pools, stakeholder voting, and coordination-game systems as possible arbitration models
    • The public monorepo README shows reality.eth is not just a contract idea but an actively maintained stack spanning contracts, libraries, dapp, docs, CLI tooling, template generation, and graph definitions
    • The official Subjectivocratic Oracle-enshrined Rollup design note extends reality.eth into a governance-relevant framing: the escalation game can act as the routine dispute layer beneath more expensive fork-or-governance escalation, which is useful for comparing oracle truth, arbitration, and governance control surfaces
  • Whitepaper: The project has an official whitepaper inside its documentation plus the related Subjectivocratic Oracle-enshrined Rollup design note from the same team; see ../whitepapers/reality-eth-primary-sources-2026-05-07.md.
  • Sources:

Internal linkages

  • Arbitration backend and court-design analogue that often sits directly behind reality.eth dispute escalation: kleros

  • Optimistic-oracle peer that likewise turns offchain truth into executable onchain outcomes through challenge windows and escalation policy: uma-optimistic-oracle-v3

  • Subjective-data oracle cousin where dispute design and governance similarly matter as much as data publication itself: tellor

  • Last reviewed: 2026-05-07 UTC