Oracle
Pronunciation: OR-uh-kul
Definition
A blockchain oracle supplies information from outside the ledger, such as asset prices, sports results or shipment status, to applications that otherwise cannot independently observe those facts.
Overview
What it means
A blockchain oracle supplies information from outside the ledger, such as asset prices, sports results or shipment status, to applications that otherwise cannot independently observe those facts. An oracle bridges an information gap, not necessarily an asset transfer.
How it works
An oracle design may use off-chain reporters, signed attestations, multiple source aggregation, on-chain contracts and freshness rules. A consuming contract should inspect the data’s units, timestamp, confidence and failure state. Multiple reporters reduce reliance on one party only when their data and infrastructure are genuinely independent.
Understanding the technical details
Oracle consumers should specify how old data can be, which price units are expected and what happens if the oracle stops responding. For a conversion quote, a five-minute-old price may be acceptable in one context and unacceptable in another. Include an upper bound for price deviation and a circuit-breaker for extreme events. If multiple independent feeds are used, understand their shared exchange sources; otherwise apparent redundancy may fail during one market outage.
Additional protocol context
The oracle problem is deciding how an on-chain application can trust external facts. Multiple operators can reduce single-party dependence, but shared data sources or software still create correlated risk. Freshness and availability matter alongside correctness.
Applications should verify the exact feed or report, source scope, decimals, timestamp, confidence, update rule, and failure behavior. High-value contracts need stale-data rejection, manipulation resistance, and fallback policy. An oracle report is evidence under a defined model, not absolute truth.
Common failures and limitations
Oracles can be manipulated by thin markets, compromised keys, collusion or common upstream feeds. Calling a system decentralized does not establish that its answer is accurate. Financial contracts need guards against stale data and extreme price movements.
Related concepts
Node, Consensus, Transaction Propagation.
Further reading
Example
A merchant contract accepts a stablecoin equal to $100 at the current exchange rate. If its price oracle has stopped updating during volatility, the contract should reject stale prices or use a pre-defined fallback rather than silently accept an old conversion rate.
Comparison
An oracle conveys external facts into a contract. A blockchain explorer reports what has already happened on-chain. Neither automatically settles the merchant’s accounting obligations.
Key Takeaway
Oracles can be manipulated by thin markets, compromised keys, collusion or common upstream feeds.
Sources
- Ethereum Documentation: Oracles — Ethereum Foundation (2026-07-30)
- Chainlink Documentation — Chainlink (2026-07-30)