What is Oracle?

How it works

Smart contracts can't reach out to the internet. To know "what's the current price of ETH," a lending protocol like Aave needs an oracle: a contract that holds an updated price, written to by off-chain operators who pull from real-world sources.

The standard design (Chainlink, Pyth, RedStone):

1. Multiple independent operators pull prices from many exchanges (Coinbase, Binance, Kraken, etc.)
2. They reach consensus on a median price
3. The aggregated value is written to an on-chain contract
4. DeFi protocols read from that contract

Different oracles update at different cadences and security models. A pricing oracle for a major asset might update every few seconds; a weather oracle for an insurance product might update once a day.

Example

A common oracle-driven flow on Aave:

1. You deposit $10k of ETH as collateral, borrow $5k of USDC
2. The protocol uses Chainlink's ETH/USD oracle to value your collateral
3. ETH price drops; oracle reports new price
4. Your loan-to-value ratio crosses the liquidation threshold (e.g., 80%)
5. Liquidators see the on-chain price and execute the liquidation, paying your debt and seizing your collateral at a discount

Without the oracle, the protocol literally couldn't know whether you should be liquidated. The oracle's job is to stay accurate and timely; a bad oracle makes the whole system unsafe.

Why it matters

Oracles are a critical security component, and oracle exploits are one of the top loss vectors in DeFi:

• Oracle manipulation attacks. Use a flash loan to push a thin DEX price 30% off market for one block, exploit a protocol that read from that DEX's spot price, repay the flash loan. Several $100M+ exploits have used this pattern (Mango Markets, bZx, others).
• Oracle delays. A slow oracle during a fast-moving market lets borrowers withdraw or close positions at stale prices. Small drift, big problem at scale.
• Single-source oracles are fragile. Reading the price from one DEX or one CEX is much weaker than aggregating from multiple sources. Chainlink became the standard largely by being aggregate-multiple by design.

Practical implications for users:

• Check what oracle a protocol uses before depositing. Aave uses Chainlink; some smaller protocols read from less-secured sources.
• Watch for liquidation cascades during volatile moves. When price moves 10%+ in minutes, oracle staleness can trigger inappropriate liquidations or miss appropriate ones.
• Cross-chain oracle bridges (Pyth, Wormhole guardian) carry their own risks; a hacked guardian set could feed bad prices to multiple chains at once.

For a healthy DeFi protocol, "what oracle does it use, who runs it, how often does it update, what's the manipulation surface" is among the first questions auditors ask. Anything that punts these answers is a place not to leave large balances.