Oracle

An oracle brings external data, usually asset prices, onto a blockchain. Smart contracts use that data to make decisions.

Blockchains cannot natively see a token’s market price. A lending market uses an oracle to value collateral. A perp venue uses one to mark positions. An options venue may use one to settle a contract.

Oracle design is a specific attack surface. A wrong or manipulated price can trigger an incorrect liquidation, allow over-borrowing, or settle a contract at the wrong value. Oracle lag can create the same problem during a fast market.

Many oracle networks combine several price sources to make manipulation harder. That reduces one risk; it does not remove smart-contract, market, or settlement risk.

Some newer designs try to reduce or remove oracle dependence entirely — see Panoptic’s oracle-free design claim for an example in the onchain options space, which derives pricing from onchain pool state instead of an external feed. That trades oracle-manipulation risk for a different risk (the underlying pool’s own liquidity and price behavior), not a strictly safer position — see our Perpetuals category page and onchain options guide for how oracle design factors into evaluating any leveraged or derivative platform.