B.BlockAxis⌕ Search
Menu

Chainlink and the oracle problem

A lending contract needs collateral prices, but its blockchain does not natively know every market price.

BeginnerContent revised · 13.09.20264 min reading · allow 5–10 more minutes for the workshopBlockAxis
← My learning journey
Workshop · 20 XP

Awarded once after a correct answer.

The question we will work through

Distinguish external facts from blockchain agreement

Useful first : What is a blockchain?

Reading path · 5 / 14 · Beginner

Key takeaway

A lending contract needs collateral prices, but its blockchain does not natively know every market price.

The essentials

A lending contract needs collateral prices, but its blockchain does not natively know every market price. An oracle supplies information from another context in a form the contract can use. This creates a distinct dependency alongside the chain’s own consensus.

How it works

Chainlink provides oracle networks and services rather than a base chain equivalent to Bitcoin or Ethereum. Off-chain components gather and process information; contracts expose results on supported networks. The exact sources, operators and update rules depend on the service.

What to watch

Blockchain consensus makes nodes agree on the published input. It does not prove that the input perfectly represents reality. A price can be stale, incorrectly scaled or based on an illiquid market. An application needs its own checks and a defined response when suitable data is unavailable.

Understand the details

A deterministic contract cannot simply fetch an arbitrary website during execution and expect every validator to receive the same answer. An oracle system makes external information available in a form contracts can consume. This introduces a chain of dependencies: original sources, collection, aggregation, delivery and interpretation by the application.

Boundaries and common mistakes

Many reporting nodes do not guarantee independent underlying sources. Several nodes can repeat the same bad exchange price. Define what the value means, when it was observed and what the contract should do when updates stop. Agreement about a reported number is not proof that the real-world event was measured correctly.

The mechanism at a glance

SEE THE CONNECTIONS

The distinction that changes the analysis

01Network agreement
02Data accuracy

Several nodes can agree on the same incorrect input. Consensus about a report does not independently verify the real-world event behind it. Ask where the observation originated and how source failures are detected before studying aggregation.

Explain it yourself

Revisit the case above. Name what is established, what remains to be checked and the evidence needed to conclude. A strong answer addresses both sides of the diagram.

Applied workshop · work at your own pace

Apply the lesson to a case

A crop-insurance contract uses rainfall from three sensors, all connected to the same weather service. Draw the apparent three-source design and its shared upstream dependency. Then identify what a service outage would affect.

Which improvement addresses source diversity rather than merely adding more reporting nodes?

Choose one answer.

Terms in this lesson
Oracle
A mechanism that supplies a contract with information originating outside its immediate execution context.
Prepare a correction note

Describe the passage and the proposed correction. This creates a local note for you to share; it sends nothing. Do not include personal or confidential information.

Sources and references

References for the mechanisms described. Numerical examples are hypothetical unless stated otherwise. Check the applicable version, network and jurisdiction.

References reviewed on 21 September 2026. All sources →