Comment on page
Data Feed
Continuous stream of off-chain data to your smart contract
A detailed example of how to use Orakl Network Data Feed can be found at example repository
data-feed-consumer.The Orakl Network Data Feed is a secure, reliable, and decentralized source of off-chain data accessible to smart contracts on-chain. The data feed is updated at predefined time intervals, as well as if the data value deviates more than a predefined threshold, to ensure that the data remains accurate and up-to-date. Data feeds can be used in many different on-chain protocols:
- Lending and borrowing
- Mirrored assets
- Stablecoins
- Asset management
- Options and futures
- and many more!
The Orakl Data Feed includes various data feeds that can be used free of charge. The currently supported data feeds can be found in tables below.
Data Feed | Aggregator | AggregatorProxy | Heartbeat (ms) |
|---|---|---|---|
BTC-USDT | 15,000 | ||
ETH-USDT | 15,000 | ||
KLAY-USDT | 15,000 | ||
MATIC-USDT | 15,000 | ||
SOL-USDT | 15,000 | ||
USDC-USDT | 15,000 | ||
DAI-USDT | 15,000 | ||
DOT-USDT | 15,000 | ||
BNB-USDT | 15,000 | ||
TRX-USDT | 15,000 | ||
BUSD-USDT | 15,000 | ||
MNR-KRW | 15,000 | ||
ADA-USDT | 15,000 | ||
ATOM-USDT | 15,000 | ||
AVAX-USDT | 15,000 | ||
DOGE-USDT | 15,000 | ||
FTM-USDT | 15,000 | ||
LTC-USDT | 15,000 | ||
PAXG-USDT | 15,000 | ||
SHIB-USDT | 15,000 | ||
UNI-USDT | 15,000 | ||
XRP-USDT | 15,000 | ||
JOY-USDT | 15,000 | ||
WEMIX-USDT | 15,000 | ||
MBX-KRW | 15,000 | ||
KSP-KRW | 15,000 | ||
BORA-KRW | 15,000 | ||
CHF-USD | 15,000 | ||
EUR-USD | 15,000 | ||
GBP-USD | 15,000 | ||
JPY-USD | 15,000 | ||
KRW-USD | 15,000 |
Data Feed | Aggregator | AggregatorProxy | Heartbeat (ms) |
|---|---|---|---|
BTC-USDT | 15,000 | ||
ETH-USDT | 15,000 | ||
KLAY-USDT | 15,000 | ||
MATIC-USDT | 15,000 | ||
SOL-USDT | 15,000 | ||
USDC-USDT | 15,000 | ||
DAI-USDT | 15,000 | ||
DOT-USDT | 15,000 | ||
BNB-USDT | 15,000 | ||
TRX-USDT | 15,000 | ||
BUSD-USDT | 15,000 | ||
MNR-KRW | 15,000 | ||
ADA-USDT | 15,000 | ||
ATOM-USDT | 15,000 | ||
AVAX-USDT | 15,000 | ||
DOGE-USDT | 15,000 | ||
FTM-USDT | 15,000 | ||
LTC-USDT | 15,000 | ||
PAXG-USDT | 15,000 | ||
SHIB-USDT | 15,000 | ||
UNI-USDT | 15,000 | ||
XRP-USDT | 15,000 | ||
JOY-USDT | 15,000 | ||
WEMIX-USDT | 15,000 | ||
MBX-KRW | 15,000 | ||
KSP-KRW | 15,000 | ||
BORA-KRW | 15,000 | ||
CHF-USD | 15,000 | ||
EUR-USD | 15,000 | ||
GBP-USD | 15,000 | ||
JPY-USD | 15,000 | ||
KRW-USD | 15,000 |
The on-chain implementation of Data Feed is composed of two smart contracts:
Aggregator and AggregatorProxy. At first,Aggregator and AggregatorProxy are deployed together in pair, representing a single data feed (e.g. temperature in Seoul or price of BTC/USD). Aggregator is being updated at regular intervals by off-chain oracles, and AggregatorProxy is used to access the submitted data to Aggregator. Deployed AggregatorProxy contract represents a consistent API to read data from the feed, and Aggregator contract can be replaced with a newer version.In the rest of the page, we will focus on how to read from data feed and explain relation between
Aggregator and AggregatorProxy.In this section, we will explain how to integrate Orakl Network data feed to your smart contract to be able to read from any data feed. We will also point out potential issues you might encounter and how to solve them.
The section is split into following topics:
The access to data feed is provided through the
AggregatorProxy address corresponding to a data feed of your choice, and IAggregator from @bisonai/orakl-contracts.import { IAggregator } from "@bisonai/orakl-contracts/src/v0.1/interfaces/IAggregator.sol";
contract DataFeedConsumer {
IAggregator internal dataFeed;
constructor(address aggregatorProxy) {
dataFeed = IAggregator(aggregatorProxy);
}
}
Data can be queried from feed using following functions:
latestRoundData() and getRoundData(roundId).The
latestRoundData function returns metadata about the latest submission.(
uint80 id,
int256 answer,
uint startedAt,
uint updatedAt,
uint80 answeredInRound
) = dataFeed.latestRoundData();
Submissions are divided into rounds and indexed by an
id. Node operators are expected to report submission in every round, and aggregate is computed from all submissions in the same round. Submissions from previous rounds can be queried through getRoundData function which requires a single extra parameter roundId. The output format is same as from latestRoundData function.uint80 roundId =
(
uint80 id,
int256 answer,
uint startedAt,
uint updatedAt,
uint80 answeredInRound
) = dataFeed.getRoundData(roundId);
The values returned from
latestRoundData() and getRoundData(roundId) functions do not include only the data feed value (=answer) at corresponding round id but also others:startedAtupdatedAtansweredInRound
startedAt represents the timestamp when the round was started. updatedAt represents the timestamp when the round was updated last time. answeredInRound is the round id in which the answer was computed.We highly recommend you to keep track of all metadata returned by bothlatestRoundData()andgetRoundData(roundId). If your application is dependent on frequent updates, you have to make sure in application layer that data returned by any of these functions is not stale.
AggregatorProxy has several other auxiliary functions that should be utilized in order to avoid any issues from misrepresenting the answer returned from data feed.All
answers are returned with a specific decimal precision that can be queried using decimals() function.uint8 decimals = dataFeed.decimals();
AggregatorProxy is always connected to a single Aggregator, but this connection is not fixed and Aggregator can be changed. If you want to make sure that you are still using the same Aggregator you can ask for the Aggregator address through aggregator() function.address currentAggregator = dataFeed.aggregator()
When deploying an
AggregatorProxy , Aggregator's address has to be specified to create a connection between the contracts. Consumer can then request data through latestRoundData or getRoundData functions, and data will be fetched from Aggregator that is represented by the aggregatorAddress.constructor(address aggregatorAddress) {
setAggregator(aggregatorAddress);
}
At times, it might be necessary to update the address of
Aggregator. If the Aggregator address is updated, a queried data feed will come from a different Aggregator than before the update. AggregatorProxy's update of Aggregator is split into two steps: proposal and confirmation. Both steps can be only executed with onlyOwner privileges.proposeAggregator stores the proposed address to storage variable and emits event about new address being proposed. function proposeAggregator(address aggregatorAddress) external onlyOwner {
sProposedAggregator = AggregatorProxyInterface(aggregatorAddress);
emit AggregatorProposed(address(sCurrentPhase.aggregator), aggregatorAddress);
}
After the new
Aggregator is proposed, one can query a new data feed through a special functions: proposedLatestRoundData and proposedGetRoundData. These functions are useful for testing a new data feed, before accepting the new proposed Aggregator.The function
confirmAggregator is used to finalize the transition to the new proposed Aggregator, and can be executed only with account that has onlyOwner privilege. New aggregator is finalized through setAggregator (called also inside of constructor of AggregatorProxy). Finally, the new aggregator is announced through emitted event.function confirmAggregator(address aggregatorAddress) external onlyOwner {
require(aggregatorAddress == address(sProposedAggregator), "Invalid proposed aggregator");
address previousAggregator = address(sCurrentPhase.aggregator);
delete sProposedAggregator;
setAggregator(aggregatorAddress);
emit AggregatorConfirmed(previousAggregator, aggregatorAddress);
}
Last modified 6d ago