From d85afa1a195142c6f222b927db89dc5da61a944f Mon Sep 17 00:00:00 2001 From: Sebastian Lerner Date: Wed, 25 Mar 2026 11:34:14 -0400 Subject: [PATCH 1/2] Data Feeds: add Bob, Katana, Sonic, TRON, Plasma, Monad to deprecating feeds chainlist Made-with: Cursor --- src/features/data/chains.ts | 42 +++++++++++++++++++++++++++++++++++++ 1 file changed, 42 insertions(+) diff --git a/src/features/data/chains.ts b/src/features/data/chains.ts index 763d501b1f2..50c3245d600 100644 --- a/src/features/data/chains.ts +++ b/src/features/data/chains.ts @@ -1036,6 +1036,48 @@ export const ALL_CHAINS: Chain[] = [ rddUrl: "https://reference-data-directory.vercel.app/feeds-solana-mainnet.json", queryString: "solana-mainnet", }, + { + name: "BOB Mainnet", + explorerUrl: "https://explorer.gobob.xyz/address/%s", + networkType: "mainnet", + rddUrl: "https://reference-data-directory.vercel.app/feeds-bitcoin-mainnet-bob-1.json", + queryString: "bob-mainnet", + }, + { + name: "Katana Mainnet", + explorerUrl: "https://explorer.katanarpc.com/address/%s", + networkType: "mainnet", + rddUrl: "https://reference-data-directory.vercel.app/feeds-polygon-mainnet-katana.json", + queryString: "katara-mainnet", + }, + { + name: "Sonic Mainnet", + explorerUrl: "https://sonicscan.org/address/%s", + networkType: "mainnet", + rddUrl: "https://reference-data-directory.vercel.app/feeds-sonic-mainnet.json", + queryString: "sonic-mainnet", + }, + { + name: "TRON Mainnet", + explorerUrl: "https://tronscan.org/#/address/%s", + networkType: "mainnet", + rddUrl: "https://reference-data-directory.vercel.app/feeds-tron-mainnet.json", + queryString: "tron-mainnet", + }, + { + name: "Plasma Mainnet", + explorerUrl: "https://plasmascan.to/address/%s", + networkType: "mainnet", + rddUrl: "https://reference-data-directory.vercel.app/feeds-plasma-mainnet.json", + queryString: "plasma-mainnet", + }, + { + name: "Monad Mainnet", + explorerUrl: "https://monadvision.com/address/%s", + networkType: "mainnet", + rddUrl: "https://reference-data-directory.vercel.app/feeds-monad-mainnet.json", + queryString: "monad-mainnet", + }, ], label: "All", }, From dfdc2a83661132cafdcafc355c91aa521726d44b Mon Sep 17 00:00:00 2001 From: Sebastian Lerner Date: Fri, 3 Apr 2026 19:08:53 -0400 Subject: [PATCH 2/2] =?UTF-8?q?docs:=20reorganize=20Selecting=20Data=20Fee?= =?UTF-8?q?ds=20=E2=80=94=20separate=20risk=20tiers=20from=20Market=20Pric?= =?UTF-8?q?e=20Feeds?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit - Add "Market pricing risk by category" section for Low through Deprecating tiers - Move "Market Price Feeds" and "Bounded Market Price Feeds" next to Exchange Rate Feeds - Preserve anchors #market-price-feeds and #bounded-market-price-feeds - Fix typo: "ice mitigation" → "risk mitigation" in Exchange Rate Feeds aside - Sync llms-full.txt with selecting-data-feeds.mdx Made-with: Cursor --- src/content/data-feeds/llms-full.txt | 30 +++++++++++-------- .../data-feeds/selecting-data-feeds.mdx | 30 +++++++++++-------- 2 files changed, 34 insertions(+), 26 deletions(-) diff --git a/src/content/data-feeds/llms-full.txt b/src/content/data-feeds/llms-full.txt index a591ccce304..6302d9a8359 100644 --- a/src/content/data-feeds/llms-full.txt +++ b/src/content/data-feeds/llms-full.txt @@ -3641,19 +3641,9 @@ Data feeds are grouped into the following categories based on the level of marke Changelog](https://dev.chain.link/changelog?product=Data+Feeds). -## Market Price Feeds - -Market Price Feeds incorporate three layers of aggregation at the data source, node operator, and oracle network layers. These feeds are designed to reflect observable market prices across [major venues](https://blog.chain.link/chainlink-price-feeds-secure-defi/). +## Market pricing risk by category -### Bounded Market Price Feeds - -Bounded Market Price Feeds are a specific category of Market Price Feeds that incorporate predefined bounds on reported values to mitigate specific asset class risks, following risk management best practices. - -For example, a Bounded Market Price Feed for a stablecoin would include an upper bound that caps the on-chain reported price at a pre-defined maximum (e.g., $1.05), even during edge cases like market dislocations where the stablecoin trades higher than the cap. In such cases, the price will not be reported on-chain. Instead, the most recently written on-chain price will be the value returned by calling [latestRoundData](https://docs.chain.link/data-feeds/api-reference#latestrounddata) on the feed’s [proxy address](https://docs.chain.link/data-feeds#single-value-feed-components). This helps prevent extreme or sustained premium pricing from being reported. These bounds are designed to provide guardrails for assets where structural deviations may introduce elevated risk for feed consumers. Note that a Bounded Market Price Feed for a stablecoin would not include a lower bound for the on-chain reported price. - -In rare circumstances, the fundamental value of an asset underlying a Bounded Market Price Feed, such as a stablecoin, may materially change. In such a case, the predefined bound(s) associated with a Bounded Market Price Feed may be adjusted or removed following advanced notice to consumers of such Bounded Market Price Feed. - -Users must be aware that Bounded Market Price Feeds have unique risk considerations. Developers remain responsible for ensuring that protocol risk parameters are configured appropriately and that the operation and performance of Bounded Market Price Feeds matches expectations. If your use case requires the use of a non-Bounded Market Price Feed and one does not exist, contact us at [chainlink_data_feeds@smartcontract.com](mailto:chainlink_data_feeds@smartcontract.com). +These subsections describe standard market price feeds at each pricing risk level and correspond to the [category list](#data-feed-categories) above. ### 🟢 Low Market Pricing Risk Feeds @@ -3871,6 +3861,20 @@ Front running (when a third party benefits from prior access to information abou To mitigate the risk associated with front running, users building highly latency-dependent applications should assess whether the configuration of data feeds meets their needed specifications for speed and frequency. [Chainlink Data Streams](https://docs.chain.link/data-streams) serve as an alternative solution to Data Feeds for latency-sensitive applications, providing low-latency delivery of market data offchain that can be verified onchain while mitigating front running. +## Market Price Feeds + +Market Price Feeds incorporate three layers of aggregation at the data source, node operator, and oracle network layers. These feeds are designed to reflect observable market prices across [major venues](https://blog.chain.link/chainlink-price-feeds-secure-defi/). + +### Bounded Market Price Feeds + +Bounded Market Price Feeds are a specific category of Market Price Feeds that incorporate predefined bounds on reported values to mitigate specific asset class risks, following risk management best practices. + +For example, a Bounded Market Price Feed for a stablecoin would include an upper bound that caps the on-chain reported price at a pre-defined maximum (e.g., $1.05), even during edge cases like market dislocations where the stablecoin trades higher than the cap. In such cases, the price will not be reported on-chain. Instead, the most recently written on-chain price will be the value returned by calling [latestRoundData](https://docs.chain.link/data-feeds/api-reference#latestrounddata) on the feed’s [proxy address](https://docs.chain.link/data-feeds#single-value-feed-components). This helps prevent extreme or sustained premium pricing from being reported. These bounds are designed to provide guardrails for assets where structural deviations may introduce elevated risk for feed consumers. Note that a Bounded Market Price Feed for a stablecoin would not include a lower bound for the on-chain reported price. + +In rare circumstances, the fundamental value of an asset underlying a Bounded Market Price Feed, such as a stablecoin, may materially change. In such a case, the predefined bound(s) associated with a Bounded Market Price Feed may be adjusted or removed following advanced notice to consumers of such Bounded Market Price Feed. + +Users must be aware that Bounded Market Price Feeds have unique risk considerations. Developers remain responsible for ensuring that protocol risk parameters are configured appropriately and that the operation and performance of Bounded Market Price Feeds matches expectations. If your use case requires the use of a non-Bounded Market Price Feed and one does not exist, contact us at [chainlink_data_feeds@smartcontract.com](mailto:chainlink_data_feeds@smartcontract.com). + ## Exchange Rate Feeds The architecture of exchange rate feeds differs from that of [Market Price Feeds](#market-price-feeds). @@ -3885,7 +3889,7 @@ Exchange rate feeds are useful in circumstances such as: diff --git a/src/content/data-feeds/selecting-data-feeds.mdx b/src/content/data-feeds/selecting-data-feeds.mdx index ca4ae89c087..c68bbbccd98 100644 --- a/src/content/data-feeds/selecting-data-feeds.mdx +++ b/src/content/data-feeds/selecting-data-feeds.mdx @@ -32,19 +32,9 @@ Data feeds are grouped into the following categories based on the level of marke Changelog](https://dev.chain.link/changelog?product=Data+Feeds). -## Market Price Feeds - -Market Price Feeds incorporate three layers of aggregation at the data source, node operator, and oracle network layers. These feeds are designed to reflect observable market prices across [major venues](https://blog.chain.link/chainlink-price-feeds-secure-defi/). +## Market pricing risk by category -### Bounded Market Price Feeds - -Bounded Market Price Feeds are a specific category of Market Price Feeds that incorporate predefined bounds on reported values to mitigate specific asset class risks, following risk management best practices. - -For example, a Bounded Market Price Feed for a stablecoin would include an upper bound that caps the on-chain reported price at a pre-defined maximum (e.g., $1.05), even during edge cases like market dislocations where the stablecoin trades higher than the cap. In such cases, the price will not be reported on-chain. Instead, the most recently written on-chain price will be the value returned by calling [latestRoundData](https://docs.chain.link/data-feeds/api-reference#latestrounddata) on the feed’s [proxy address](https://docs.chain.link/data-feeds#single-value-feed-components). This helps prevent extreme or sustained premium pricing from being reported. These bounds are designed to provide guardrails for assets where structural deviations may introduce elevated risk for feed consumers. Note that a Bounded Market Price Feed for a stablecoin would not include a lower bound for the on-chain reported price. - -In rare circumstances, the fundamental value of an asset underlying a Bounded Market Price Feed, such as a stablecoin, may materially change. In such a case, the predefined bound(s) associated with a Bounded Market Price Feed may be adjusted or removed following advanced notice to consumers of such Bounded Market Price Feed. - -Users must be aware that Bounded Market Price Feeds have unique risk considerations. Developers remain responsible for ensuring that protocol risk parameters are configured appropriately and that the operation and performance of Bounded Market Price Feeds matches expectations. If your use case requires the use of a non-Bounded Market Price Feed and one does not exist, contact us at [chainlink_data_feeds@smartcontract.com](mailto:chainlink_data_feeds@smartcontract.com). +These subsections describe standard market price feeds at each pricing risk level and correspond to the [category list](#data-feed-categories) above. ### 🟢 Low Market Pricing Risk Feeds @@ -261,6 +251,20 @@ Front running (when a third party benefits from prior access to information abou To mitigate the risk associated with front running, users building highly latency-dependent applications should assess whether the configuration of data feeds meets their needed specifications for speed and frequency. [Chainlink Data Streams](https://docs.chain.link/data-streams) serve as an alternative solution to Data Feeds for latency-sensitive applications, providing low-latency delivery of market data offchain that can be verified onchain while mitigating front running. +## Market Price Feeds + +Market Price Feeds incorporate three layers of aggregation at the data source, node operator, and oracle network layers. These feeds are designed to reflect observable market prices across [major venues](https://blog.chain.link/chainlink-price-feeds-secure-defi/). + +### Bounded Market Price Feeds + +Bounded Market Price Feeds are a specific category of Market Price Feeds that incorporate predefined bounds on reported values to mitigate specific asset class risks, following risk management best practices. + +For example, a Bounded Market Price Feed for a stablecoin would include an upper bound that caps the on-chain reported price at a pre-defined maximum (e.g., $1.05), even during edge cases like market dislocations where the stablecoin trades higher than the cap. In such cases, the price will not be reported on-chain. Instead, the most recently written on-chain price will be the value returned by calling [latestRoundData](https://docs.chain.link/data-feeds/api-reference#latestrounddata) on the feed’s [proxy address](https://docs.chain.link/data-feeds#single-value-feed-components). This helps prevent extreme or sustained premium pricing from being reported. These bounds are designed to provide guardrails for assets where structural deviations may introduce elevated risk for feed consumers. Note that a Bounded Market Price Feed for a stablecoin would not include a lower bound for the on-chain reported price. + +In rare circumstances, the fundamental value of an asset underlying a Bounded Market Price Feed, such as a stablecoin, may materially change. In such a case, the predefined bound(s) associated with a Bounded Market Price Feed may be adjusted or removed following advanced notice to consumers of such Bounded Market Price Feed. + +Users must be aware that Bounded Market Price Feeds have unique risk considerations. Developers remain responsible for ensuring that protocol risk parameters are configured appropriately and that the operation and performance of Bounded Market Price Feeds matches expectations. If your use case requires the use of a non-Bounded Market Price Feed and one does not exist, contact us at [chainlink_data_feeds@smartcontract.com](mailto:chainlink_data_feeds@smartcontract.com). + ## Exchange Rate Feeds The architecture of exchange rate feeds differs from that of [Market Price Feeds](#market-price-feeds). @@ -275,7 +279,7 @@ Exchange rate feeds are useful in circumstances such as: