What an oracle reports
Smart contracts cannot directly observe external market prices, so they may rely on an oracle for values such as collateral prices. Contracts can use those inputs to set borrowing limits and trigger liquidations, making source selection, update frequency, outlier handling, and fallback behavior important. An oracle value is not necessarily a price available across the market.
Spot prices and reference markets
In protocol documentation, identify feed providers, aggregation, minimum responses, heartbeat and deviation thresholds, and emergency pause authority. A token trading in a shallow market can move sharply on a small order. Compare the exchanges, pools, and pairs referenced by the oracle with liquidity in the market where liquidation would occur.
Liquidity and price impact
If a hypothetical collateral pool is thin and an attacker moves its price briefly before a contract updates, unfair liquidations or bad debt may result. Time-weighted averages and multiple feeds can reduce some risks but cannot prevent every manipulation or abrupt market move. Review liquidation rules, delays, and recovery procedures as well.
A hypothetical liquidation
Two feeds may not be independent if both reference the same exchange and market. Review correlation among sources, whether stale values are reused, and how the contract behaves when updates fail.
Check feeds and heartbeats
In a hypothetical stress test, ask whether liquidation orders intensify a price shock as volume falls and collateral drops. Linking oracle risk bands with liquidation penalties and auction mechanics clarifies where losses could compound.
Cascading risk and response
Normal-period accuracy or an audit history does not guarantee correct pricing for every asset and market condition. New feed listings, administrator keys, or changes in quote currency can alter risk. Before using a protocol, separately assess real collateral liquidity and the pause or recovery path if the oracle fails.