Why contracts need outside data
A smart contract cannot independently observe an off-chain market price. Lending, insurance, and derivatives applications rely on an oracle to deliver external data, and the quality of that input can change the contract's outcome.
How a price reaches a contract
a blockchain does not know an outside market price or weather result by itself, so an oracle supplies the input. The number of providers, aggregation method, refresh interval, and halt rules can directly affect a contract outcome. A displayed estimate assumes conditions at one moment, so it should not be treated as identical to the final execution, settlement, or withdrawal result.
Stale or distorted inputs
a fast market, an unavailable provider, a stale value, or a distorted reference venue can trigger liquidation, collateral, or settlement differently from what users expect. Correct contract code does not remove input-data risk. Consider separately the cases in which price moves, network congestion, shrinking liquidity, and a change in operating authority happen at the same time.
A hypothetical liquidation threshold
If a lending contract uses a price feed to trigger liquidation, the gap between the live market and a stale feed can change the outcome. Check update intervals, deviation limits, and halt conditions during fast markets, then determine whether the contract continues using the last value after updates stop. Correct code cannot repair inaccurate input by itself.
Check feed health and authority
identify the feed and reference markets, last update time, deviation guardrails, emergency authority, and the documented response to an outage in both product documentation and on-chain configuration. Match official documentation with the on-chain address first, and avoid connecting a wallet through search advertising or a link with a similar name.
How a delayed feed can affect a threshold
In a hypothetical loan near its liquidation threshold, the market may move before the price feed updates, leaving the contract to act on an older value. Review not only update delay but also deviation limits and behavior when updates stop.
Test the outage behavior
Check more than the oracle's name: identify reference markets, update times, deviation limits, outage behavior, and administrative controls. Correct contract code can still produce a different result when its input is delayed or inaccurate.