جلب البيانات خارج السلسلة

Smart contracts are powerful, but they operate in isolation on the blockchain. They can't directly access information from the 'real world' like current stock prices, weather data, or external API responses.

This limitation is known as the oracle problem. To overcome it, we use oracles.

Chainlink is a decentralized oracle network designed to securely connect smart contracts with off-chain data and services.

• It acts as a bridge between the blockchain and external systems.
• Chainlink nodes collect data from various sources.
• They then deliver this data to smart contracts in a reliable and verifiable way.

One of the most common and critical uses of Chainlink is providing price feeds. These feeds deliver up-to-date market prices for cryptocurrencies, commodities, and other assets directly to your smart contracts.

This is crucial for DeFi applications, lending protocols, and derivatives.

To get data from a Chainlink price feed, your smart contract interacts with a specific data feed contract deployed on the blockchain.

These data feed contracts all implement a standard interface called AggregatorV3Interface. This makes it easy for your contract to read the data.

The primary function we use to fetch the latest price from an AggregatorV3Interface is latestRoundData().

It returns several pieces of information, including the actual price, when it was updated, and the round ID.

Let's write a simple Solidity contract that reads the latest ETH/USD price from a Chainlink price feed. You can try running this in Remix, using the Sepolia testnet.

The address 0x694AA1769357215Ee4f0fFf93d2d05d454e5f5c4 is for the ETH/USD price feed on Sepolia.

The answer returned by latestRoundData() is the actual price, but it's an int and scaled by a certain number of decimals.

You must call getDecimals() to know how many decimal places to account for. For example, if answer is 180000000000 and decimals is 8, the price is 1800.00000000.

While price feeds are common, Chainlink can also fetch almost any other type of off-chain data, or even generate verifiable randomness.

This requires a more generalized approach where your contract makes a request to a Chainlink node for specific data, and the node responds by calling back your contract.

For custom data, Chainlink uses a two-step process:

1. Request: Your smart contract sends a request to a Chainlink oracle contract, specifying the data source (e.g., an API endpoint) and the job ID.
2. Fulfill: A Chainlink node processes the request, fetches the off-chain data, and then sends a transaction back to your smart contract, calling a designated 'fulfill' function with the requested data.

This ensures data is delivered securely on-chain.

Consider a smart contract that needs to get the current weather conditions for a specific city. Which of the following best describes how a Chainlink oracle would typically facilitate this?

We've explored how smart contracts fetch off-chain data using Chainlink. You learned about:

• The oracle problem and Chainlink's solution.
• Interacting with Chainlink Price Feeds using AggregatorV3Interface.
• The latestRoundData() function and interpreting its output.
• The general 'request and fulfill' pattern for custom data requests.

Fetching external data securely is vital for building robust DApps!