In simple terms — A blockchain oracle is a bridge for information. It supplies a smart contract with a price, rate, outcome, or other fact that the blockchain cannot learn directly.
An oracle does not necessarily predict the future. Its role is to produce data that a contract can use under defined rules. Without this infrastructure, a lending protocol could not know the external value of collateral, and a derivative would not have the reference needed to calculate settlement.
From external data to the smart contract
The process has several stages: obtain information from one or more sources, check or aggregate it, sign or transmit the result, and publish it on the blockchain. The consuming contract then reads the value and decides whether to trigger a liquidation, allow a loan, or settle a position.
Oracles differ in their sources, architecture, and trust model. They may use a single operator or a network of nodes; they may update a feed periodically, on request, or when the value exceeds a deviation threshold. Some oracles use data already available onchain, such as a price observed in a liquidity pool. “Decentralized” describes the distribution of certain functions; by itself, it does not guarantee correct data.
Freshness, liquidity, and manipulation
Authentic but stale data can be as unsuitable as false data. The contract must know when the feed was last updated and decide what to do if it is delayed. Averaging several observations can reduce some distortions, but it does not make the system immune to manipulation.
An attacker can target the oracle or the market from which it reads. If a protocol uses the spot price of a thin liquidity pool, a temporary trade can distort the reference and trigger liquidations or loans on incorrect terms. Capital obtained through a flash loan can make this sequence executable within one transaction, without implying that every flash loan is an attack.
Reading a protocol's feed dependency
Assessing a protocol requires identifying the price source, aggregation method, update frequency or threshold, deviation controls, and behavior when data is unavailable. The accounts allowed to replace the feed, change its parameters, or pause the contract also matter.
A fallback can maintain service during a failure, but it introduces another dependency. The useful question is therefore not only “which oracle does it use?” but which data, controls, and administrative powers connect the feed to the financial decision.
Sources
- Ethereum.org — Oracles — Defines oracles, source and trust models, and the flow of offchain data into smart contracts.
- BIS Bulletin 76 — The oracle problem and the future of DeFi — Examines oracle dependency, manipulation, and the trade-off between efficiency and decentralization in DeFi.
Related entries
Blockchain bridges · Smart contract risk · Flash loans · Decentralized finance (DeFi)