FOLLOW THE MECHANISM
- 1Observe
Sources measure an outside event or market.
- 2Report
A mechanism aggregates and publishes an assertion.
- 3Consume
The contract interprets units, time and validity.
- 4Act
Prices or conditions affect borrowing, liquidation or settlement.
A conceptual sequence. Real implementations can add steps, intermediaries, and conditions.
The boundary between execution and observation
Smart contracts can verify signatures and execute deterministic rules, but they cannot directly observe a bank account, a weather event or a global asset price. An oracle supplies information through an onchain interface. The chain can agree that a particular value was published by the expected mechanism while the value itself remains incomplete, delayed or incorrect. This distinction is essential: agreement about received data and truth about the external world are separate problems.
A price is a designed measurement
A feed may combine data vendors, exchanges and reporting nodes, applying aggregation and update rules. Chainlink’s documentation describes multiple feed types and emphasizes developer responsibilities when integrating them. A consumer needs to understand denomination, decimal precision, update timing and what the value represents. A market price, a redemption exchange rate and a reserve attestation answer different questions. Substituting one for another can change when a loan liquidates or whether a token appears adequately backed.
Manipulation and staleness have different causes
A thin pool’s immediate price can be moved temporarily by a large trade. Averaging over time can make some manipulation harder, while introducing delay. Multiple reporters can reduce dependence on one reporter without fixing common data-source failures. A stale but once-correct value can be dangerous during rapid market movement. A feed on a layer-two network may also need handling for sequencer downtime and resumption. There is no single oracle architecture that removes all of these trade-offs.
Trace the consequence of a bad input
In a lending protocol, an overstated collateral price may allow excessive borrowing; an understated price may trigger premature liquidation. In a derivative, the reference price can affect margin and settlement. The application must decide how to behave when data is unavailable or outside expected bounds: pause, fall back or continue, each with consequences. An oracle failure should therefore be shown as a concrete path from a measurement to a contract decision, rather than buried in a generic technology warning.
MAKE IT CONCRETE
Illustrative unit error
A feed reports 200,000,000 with eight decimals, meaning 2.00. Reading it as an unscaled integer overstates the price by 100 million times. Correct signatures cannot repair a consumer’s unit mistake.
FAILURE PATHS & COMMON MISREADINGS
Where the model can break
- Many reporters can still share one flawed underlying source.
- An oracle price is not necessarily an executable sale price.
KEEP EXPLORING