Distinguish external facts from blockchain agreement
By the end, explain the diagram in your own words, solve the case and justify the correction.
Prerequisites : What is a blockchain?
Level 1 · Beginner →Reading path · 5 / 12 · Beginner
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
- External observation
- Collection and aggregation
- Oracle report
- Contract interpretation
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.
Use independently operated measurement sources where feasible and specify discrepancy handling. Adding a fourth copy of the same service does not remove the shared dependency. Also define observation windows and missing-data behavior; a fallback value can itself create exploitable assumptions.
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.