Skip to article
Degrees of SatoshiFollow the connections.
SearchTrace an address
Degrees of Satoshi/ Encyclopedia

Encyclopedia DeFi · Entry 59

Blockchain oracles: getting observations into contract decisions

AI-assisted research · separate automated verificationCorrections

Theme
DeFi
Sources
3 cited records
Reading time
About 3 minutes
Automated verification
Substantive update
In this article

At a glance

Key facts

Key facts for Blockchain oracles: getting observations into contract decisions
FactDetailSource
BoundaryRecording data on-chain does not prove its external truth.[1]
ScalingFeed decimals are needed to interpret a reported answer.[2]
FreshnesslatestRoundData exposes an updatedAt timestamp.[2]
01

A price can decide a financial state transition

A lending contract needs a common unit to compare collateral with debt. The balances may be on-chain, but their relative market value comes from observations. A price feed supplies the value used in that calculation.

The contract checks rules against its supplied input. If that input is stale, manipulated or scaled incorrectly, otherwise consistent code can produce an inappropriate result. Consensus on execution and correctness of the observation are separate properties.

02

Interpret a value together with its metadata

Suppose a hypothetical feed reports 250,000,000 and specifies eight decimals. The represented value is 2.5 quote units, not 250 million. The token’s own decimals need not match the feed’s decimals.

A timestamp establishes when a reported observation was updated. It does not by itself state whether that age is acceptable: the application needs a policy suitable for the feed’s update model and the decision being made. Chainlink’s cited interface exposes these fields but does not choose every integrator’s limits.

03

Read the specific feed’s assumptions

Identify which market and asset a feed measures, the data providers or aggregation process, update conditions and what the consuming application does on failure. A feed for an underlying asset is not automatically a price for a bridged claim or a receipt token.

Redundancy can reduce some failure modes while leaving shared dependencies. Several data paths that ultimately depend on the same thin market can share the same weakness. Inspect sources and economic context rather than count endpoints.

Direct answers

Questions people ask

Can a blockchain prove an oracle’s price is correct?

It can verify the on-chain computation or signatures required by that oracle design. That does not by itself prove that the outside market observation accurately represents the intended asset and time.

Inspect the evidence

The answer and key facts have stable claim links. These records retain the scope and qualification when reused.

An oracle supplies information that a contract cannot obtain directly from its own chain state, such as an external market price. Blockchain consensus can agree on the stored answer without proving the outside fact is correct. A usable feed also needs the right asset, units, update timing and failure handling.

Scope: DeFi. Verification: verified · 2026-10-02T15:08:18.373Z.

Link to this claim
Boundary: Recording data on-chain does not prove its external truth.

Scope: DeFi. Verification: verified · 2026-10-02T15:08:18.373Z.

Link to this claim
Scaling: Feed decimals are needed to interpret a reported answer.

Scope: DeFi. Verification: verified · 2026-10-02T15:08:18.373Z.

Link to this claim
Freshness: latestRoundData exposes an updatedAt timestamp.

Scope: DeFi. Verification: verified · 2026-10-02T15:08:18.373Z.

Link to this claim
Revision history
  1. — First publication after primary-source research and independent automated verification.
  2. — Before first publication, independent review checked and revised: sources. Read Ethereum’s oracle boundary/problem and Chainlink decimals/latestRoundData plus feed-category/integration risks. Recomputed250000000/10^8=2.5. QA, facts and limitations distinguish consensus on recorded data from external truth and correctly require asset/units/freshness scope. Tightened source locator to actual Market pricing risk headings.

Source register

Sources and references

Retrieval dates and locators are recorded individually.
  1. Oraclesethereum.org contributors

    External observations and the trust boundary between data and consensus.

    Locator: What is an oracle?; The oracle problem · Retrieved: 2026-10-02Open source
  2. Data Feeds API ReferenceChainlink

    Feed values, decimal scaling and the updatedAt timestamp.

    Locator: decimals; latestRoundData · Retrieved: 2026-10-02Open source
  3. Selecting Quality Data FeedsChainlink

    Feed-specific assumptions, liquidity and integration risk.

    Locator: Data Feed Categories; Market pricing risk by category; Risk Mitigation · Retrieved: 2026-10-02Open source
How this article was made

Research and drafting use AI assistance. A separate automated review checks claims against primary sources; no external expert or named human review is implied. Publication, substantive editing, source retrieval and verification are recorded separately. This version was independently checked by an automated reviewer on 2 October 2026.

Editorial method and corrections

Degrees of Satoshi editorial project. “Blockchain oracles: getting observations into contract decisions.” Published 2026-10-02; updated 2026-10-02. https://degreesofsatoshi.com/encyclopedia/blockchain-oracles/