Oracles

The chain cannot look outside

A contract can verify events in its own state. It cannot directly observe the dollar price of ether, the weather, an election result, or whether a shipment arrived. An oracle imports a statement about that world. Once imported, the contract may act with perfect consistency on information whose truth was established elsewhere.

Consensus is not correspondence

Multiple data sources and nodes can reduce dependence on one reporter. Agreement helps only if sources are sufficiently independent and resistant to manipulation. Five feeds copying the same thin market do not become five independent witnesses. Aggregation can filter outliers; it cannot guarantee that the surviving value corresponds to reality.

Incentives have a direction

Oracle systems pay operators, select markets, define update thresholds, and sometimes remain silent when fees or conditions do not justify an update. These choices determine which errors are likely and who bears them. A price is never just a number; it is a chain of observation, payment, timing, and fallback rules.

The seam is the product

An oracle is not an embarrassing compromise in an otherwise trustless system. It is an explicit institution for joining two domains that validate differently. Its quality should be judged by how clearly it exposes that seam: sources, latency, failure modes, governance, and the parties left holding a position when the reported world and the lived world diverge.