rewards-eligibility-oracle-primary-sources-2026-05-11

Rewards Eligibility Oracle primary sources

Last reviewed: 2026-05-11 UTC

What this file is

A compact source map for the Rewards Eligibility Oracle (REO) pass. The strongest primary materials were the approved GIP, official repository docs, eligibility-criteria document, technical design writeup, dashboard README, and The Graph technical roadmap.

Primary sources reviewed

• Governance forum thread: https://forum.thegraph.com/t/gip-0079-indexer-rewards-eligibility-oracle/6734
• Approved GIP: https://raw.githubusercontent.com/graphprotocol/graph-improvement-proposals/main/gips/0079.md
• Official REO repo README: https://raw.githubusercontent.com/graphprotocol/rewards-eligibility-oracle/main/README.md
• Eligibility criteria: https://raw.githubusercontent.com/graphprotocol/rewards-eligibility-oracle/main/ELIGIBILITY_CRITERIA.md
• Technical design: https://raw.githubusercontent.com/graphprotocol/rewards-eligibility-oracle/main/docs/technical-design.md
• REO repo: https://github.com/graphprotocol/rewards-eligibility-oracle
• Dashboard README: https://raw.githubusercontent.com/graphprotocol/rewards-eligibility-oracle-dashboard/main/README.md
• Dashboard repo: https://github.com/graphprotocol/rewards-eligibility-oracle-dashboard
• The Graph technical roadmap: https://thegraph.com/blog/technical-roadmap/
• RewardsManager contract reference: https://raw.githubusercontent.com/graphprotocol/contracts/main/packages/contracts/contracts/rewards/RewardsManager.sol

Notes pulled forward

• GIP-0079 frames REO as a two-part system: off-chain oracle nodes assess service quality, and an on-chain oracle contract stores time-bounded eligibility checked by Rewards Manager at claim time.
• The GIP and criteria doc show that the initial thresholds are intentionally conservative: 5 active days in a 28-day window, at least one qualifying query per counted day, HTTP 200, latency under 5 seconds, and freshness within 50,000 blocks of chainhead.
• The technical design doc makes the operations stack legible: daily scheduling, BigQuery input, CSV artifacts, batched onchain renewals, RPC failover, Slack alerts, and a circuit breaker to avoid wasteful restart loops.
• The GIP makes two crucial safety valves explicit: governance can disconnect the oracle from Rewards Manager, and the oracle can fail open if no updates arrive within the timeout.
• The roadmap positions REO alongside chain integrations and Indexing Payments as part of The Graph’s attempt to better align indexer incentives with real service quality.

Why it matters

REO is a distinct incentive-control layer inside The Graph stack. It sits between data-service performance and inflationary rewards, which makes it a more useful analytical object than treating it as a mere dashboard or ops script.