diff --git a/docs/data/oracles/oracle-providers.mdx b/docs/data/oracles/oracle-providers.mdx index 37e105f6a7..1ab4f37f14 100644 --- a/docs/data/oracles/oracle-providers.mdx +++ b/docs/data/oracles/oracle-providers.mdx @@ -148,3 +148,20 @@ To integrate, see the [Pyth Pro Stellar integration guide](https://docs.pyth.net | --- | --- | | [`CACZ3GBAKUPIAFRILUFO27J5RUH5GJ2VSJ46LP6GJYSKGDRTQ5MS3HCH`](https://stellar.expert/explorer/public/contract/CACZ3GBAKUPIAFRILUFO27J5RUH5GJ2VSJ46LP6GJYSKGDRTQ5MS3HCH) | Mainnet | | [`CAYFT5JE3UQTKT4Q6ZOZK4FXVYVT6RE3MFC7STA4UB6WAEGBT65MRU52`](https://stellar.expert/explorer/testnet/contract/CAYFT5JE3UQTKT4Q6ZOZK4FXVYVT6RE3MFC7STA4UB6WAEGBT65MRU52) | Testnet | + +## [Chainlink](https://chain.link) + +Chainlink is an oracle platform that provides market data and other services to smart contracts across many blockchains. On Stellar, [Chainlink Data Feeds](https://docs.chain.link/data-feeds/stellar) and [Chainlink Data Streams](https://docs.chain.link/data-streams/tutorials/stellar-onchain-report-verification) are live. Read the [launch announcement](https://stellar.org/blog/foundation-news/chainlink-is-now-live-on-stellar-unleashing-a-new-wave-of-defi-innovation) on the Stellar blog. + +Data Feeds on Stellar use a single proxy contract that serves every feed. Instead of a per-feed contract address, a consumer selects a feed by its 32-byte `data_id`, which is the **Feed ID** listed on the [Chainlink price feed addresses page](https://docs.chain.link/data-feeds/price-feeds/addresses?network=stellar) with Stellar selected. The proxy is not SEP-40 compatible. Consumers call `latest_round(data_id, decimals)` or `get_round(data_id, round_id, decimals)`, and each round returns a `round_id`, an `answer` (`I256`), and a `timestamp`. Answers are stored at 18 decimal places. Pass `18` as `decimals` unless Chainlink has approved a reduced precision for the feed. + +Data Streams uses a pull model. Applications fetch signed reports off-chain and verify them on-chain through the Chainlink Verifier contract. Using Data Streams requires an account allowlisted by Chainlink. + +To integrate, see [Using Data Feeds Offchain](https://docs.chain.link/data-feeds/stellar/using-data-feeds-off-chain), [Using Data Feeds Onchain](https://docs.chain.link/data-feeds/stellar/using-data-feeds-on-chain), and [Verify Data Streams reports onchain (Stellar)](https://docs.chain.link/data-streams/tutorials/stellar-onchain-report-verification). The proxy interface is defined in the [chainlink-stellar](https://github.com/smartcontractkit/chainlink-stellar) repository. + +### Deployed Chainlink Data Feeds proxy contracts + +| Address | Contract | Network | +| --- | --- | --- | +| [`CDQBHEUGLDHMSUHG4IH33RJBUTMNCZOT4JIAQR4WZFRDZW6DR6S32ZLZ`](https://stellar.expert/explorer/public/contract/CDQBHEUGLDHMSUHG4IH33RJBUTMNCZOT4JIAQR4WZFRDZW6DR6S32ZLZ) | Data Feeds proxy (all feeds) | Mainnet | +| [`CBUF6IADAWPWIDWRTHJNINKXHG2UTIQ6TU2F2HRAXWAI7OT3KJPKK6O4`](https://stellar.expert/explorer/testnet/contract/CBUF6IADAWPWIDWRTHJNINKXHG2UTIQ6TU2F2HRAXWAI7OT3KJPKK6O4) | Data Feeds proxy (all feeds) | Testnet |