Data: Batch of quality, sourcing, and usage updates

reports/llms-report.json

@@ -1,5 +1,5 @@
 {
-  "startedAt": "2025-11-24T20:57:41.455Z",
+  "startedAt": "2025-11-25T23:16:10.318Z",
   "siteBase": "https://docs.chain.link",
   "sections": [
     {
@@ -30,25 +30,25 @@
       "section": "ccip",
       "pagesProcessed": 260,
       "outputPath": "src/content/ccip/llms-full.txt",
-      "bytes": 2847128,
-      "prevBytes": 2847128,
+      "bytes": 2849278,
+      "prevBytes": 2849278,
       "deltaBytes": 0
     },
     {
       "section": "data-feeds",
-      "pagesProcessed": 35,
+      "pagesProcessed": 37,
       "outputPath": "src/content/data-feeds/llms-full.txt",
-      "bytes": 291525,
-      "prevBytes": 291525,
+      "bytes": 302350,
+      "prevBytes": 302350,
       "deltaBytes": 0
     },
     {
       "section": "data-streams",
-      "pagesProcessed": 53,
+      "pagesProcessed": 54,
       "outputPath": "src/content/data-streams/llms-full.txt",
-      "bytes": 474463,
-      "prevBytes": 474592,
-      "deltaBytes": -129
+      "bytes": 477065,
+      "prevBytes": 477061,
+      "deltaBytes": 4
     },
     {
       "section": "dta-technical-standard",
@@ -123,5 +123,5 @@
       "deltaBytes": 0
     }
   ],
-  "finishedAt": "2025-11-24T20:57:45.128Z"
+  "finishedAt": "2025-11-25T23:16:13.816Z"
 }

src/config/sidebar.ts

@@ -545,35 +545,28 @@ export const SIDEBAR: Partial<Record<Sections, SectionEntry[]>> = {
           url: "data-feeds/developer-responsibilities",
         },
         {
-          title: "Price Feeds",
-          url: "data-feeds/price-feeds",
-        },
-        {
-          title: "SmartData",
-          url: "data-feeds/smartdata",
+          title: "Feed Types",
+          url: "data-feeds/feed-types",
           children: [
+            { title: "Price Feeds", url: "data-feeds/price-feeds" },
             {
-              title: "Multiple-Variable Response (MVR) Feeds",
-              url: "data-feeds/mvr-feeds",
+              title: "SmartData",
+              url: "data-feeds/smartdata",
+              children: [{ title: "Multiple-Variable Response (MVR) Feeds", url: "data-feeds/mvr-feeds" }],
             },
+            { title: "Smart Value Recapture (SVR) Feeds", url: "data-feeds/svr-feeds" },
+            { title: "Rate and Volatility Feeds", url: "data-feeds/rates-feeds" },
+            { title: "L2 Sequencer Uptime Feeds", url: "data-feeds/l2-sequencer-feeds" },
           ],
         },
-        {
-          title: "Smart Value Recapture (SVR) Feeds",
-          url: "data-feeds/svr-feeds",
-        },
-        {
-          title: "Rate and Volatility Feeds",
-          url: "data-feeds/rates-feeds",
-        },
-        {
-          title: "L2 Sequencer Uptime Feeds",
-          url: "data-feeds/l2-sequencer-feeds",
-        },
         {
           title: "Flags Contract Registry",
           url: "data-feeds/contract-registry",
         },
+        {
+          title: "Data Sources",
+          url: "data-feeds/data-sources",
+        },
         {
           title: "Release Notes",
           url: "https://dev.chain.link/changelog?product=Data+Feeds",
@@ -823,6 +816,10 @@ export const SIDEBAR: Partial<Record<Sections, SectionEntry[]>> = {
           title: "Billing",
           url: "data-streams/billing",
         },
+        {
+          title: "Data Sources",
+          url: "data-streams/data-sources",
+        },
         {
           title: "Release Notes",
           url: "https://dev.chain.link/changelog?product=Data+Streams",

src/content/chainlink-local/llms-full.txt

@@ -7712,7 +7712,7 @@ The `prepareScenario()` function is invoked at the beginning of each test case.
    sourceCCIPBnMToken.approve(address(sourceRouter), amountToSend);
    ```
 
-3. Create an array [Client.EVMTokenAmount](/ccip/api-reference/evm/v1.6.2/client#evmtokenamount)[] to specify the token transfer details. This array and the amount to send
+3. Create an array [Client.EVMTokenAmount](/ccip/api-reference/evm/v1.6.1/client#evmtokenamount)[] to specify the token transfer details. This array and the amount to send
    are returned by the `prepareScenario()` function for use in the calling test case:
 
    ```solidity
@@ -7759,7 +7759,7 @@ Here are the steps involved in this test case:
    ccipLocalSimulatorFork.requestLinkFromFaucet(alice, 10 ether);
    ```
 
-5. Construct the [Client.EVM2AnyMessage](/ccip/api-reference/evm/v1.6.2/client#evm2anymessage) structure with the receiver, token amounts, and other necessary details.
+5. Construct the [Client.EVM2AnyMessage](/ccip/api-reference/evm/v1.6.1/client#evm2anymessage) structure with the receiver, token amounts, and other necessary details.
 
    - Set the `data` parameter to an empty string because you are not sending any arbitrary data, only tokens.
    - In `extraArgs`, set the gas limit to `0`. This gas limit is for execution of receiver logic, which doesn't apply here because you're sending tokens to an EOA.
@@ -7832,7 +7832,7 @@ Here are the steps involved in this test case:
    deal(alice, 5 ether);
    ```
 
-5. Construct the [Client.EVM2AnyMessage](/ccip/api-reference/evm/v1.6.2/client#evm2anymessage) structure. This step is the same as in the previous test case.
+5. Construct the [Client.EVM2AnyMessage](/ccip/api-reference/evm/v1.6.1/client#evm2anymessage) structure. This step is the same as in the previous test case.
    The main difference is that the `feeToken` is set with `address(0)` to indicate that the fees are paid in native gas:
 
    ```solidity
@@ -7993,7 +7993,7 @@ The `prepareScenario()` function is invoked at the beginning of each test case.
    ccipBnMToken.approve(address(router), amountToSend);
    ```
 
-3. Create an array [Client.EVMTokenAmount](/ccip/api-reference/evm/v1.6.2/client#evmtokenamount)[] to specify the token transfer details. This array and the amount to send are returned by the prepareScenario() function for use in the calling test case:
+3. Create an array [Client.EVMTokenAmount](/ccip/api-reference/evm/v1.6.1/client#evmtokenamount)[] to specify the token transfer details. This array and the amount to send are returned by the prepareScenario() function for use in the calling test case:
 
    ```solidity
    tokensToSendDetails = new Client.EVMTokenAmount[](1);
@@ -8032,7 +8032,7 @@ Here are the steps involved in this test case:
    ccipLocalSimulator.requestLinkFromFaucet(alice, 5 ether);
    ```
 
-5. Construct the [Client.EVM2AnyMessage](/ccip/api-reference/evm/v1.6.2/client#evm2anymessage) structure with the receiver, token amounts, and other necessary details.
+5. Construct the [Client.EVM2AnyMessage](/ccip/api-reference/evm/v1.6.1/client#evm2anymessage) structure with the receiver, token amounts, and other necessary details.
 
    - Set the `data` parameter to an empty string because you are not sending any arbitrary data, only tokens.
    - In `extraArgs`, set the gas limit to `0`. This gas limit is for execution of receiver logic, which doesn't apply here because you're sending tokens to an EOA.
@@ -8096,7 +8096,7 @@ Here are the steps involved in this test case:
    deal(alice, 5 ether);
    ```
 
-4. Construct the [Client.EVM2AnyMessage](/ccip/api-reference/evm/v1.6.2/client#evm2anymessage) structure. This step is the same as in the previous test case.
+4. Construct the [Client.EVM2AnyMessage](/ccip/api-reference/evm/v1.6.1/client#evm2anymessage) structure. This step is the same as in the previous test case.
    The main difference is that the `feeToken` is set with `address(0)` to indicate that the fees are paid in native gas:
 
    ```solidity
@@ -8429,7 +8429,7 @@ while paying fees in LINK. Here are the steps involved in this test case:
    ]
    ```
 
-6. Construct the [Client.EVM2AnyMessage](/ccip/api-reference/evm/v1.6.2/client#evm2anymessage) structure with the receiver, token amounts, and other necessary details.
+6. Construct the [Client.EVM2AnyMessage](/ccip/api-reference/evm/v1.6.1/client#evm2anymessage) structure with the receiver, token amounts, and other necessary details.
 
    - Use an empty string for the `data` parameter because you are not sending any arbitrary data (only tokens).
    - Set `gasLimit` to `0` because you are sending tokens to an EOA, which means you do not expect any execution of receiver logic (and therefore do not need gas for that).

src/content/data-feeds/data-sources.mdx

@@ -0,0 +1,65 @@
+---
+section: dataFeeds
+date: Last Modified
+title: "Data Sources"
+metadata:
+  title: "Data Sources | Chainlink Data Feeds"
+  description: "Reference overview of data sourcing for Chainlink Data Feeds asset and product types."
+  keywords:
+    [
+      "Data Sources",
+      "Data Feeds",
+      "Data Streams",
+      "Crypto Price",
+      "Crypto State Price",
+      "Forex",
+      "Precious Metals",
+      "US Oil",
+      "US Equities",
+      "UK ETFs",
+      "Euro ETFs",
+      "Proof of Reserve",
+      "Cross Chain PoR",
+      "NAV",
+      "Exchange Rate",
+      "MarketCap",
+      "Composite Index",
+      "Central Bank Rates",
+      "Crypto LWBA",
+      "Data Link Long Tail Crypto",
+    ]
+---
+
+import Aside from "@components/Aside.astro"
+
+Chainlink Data Feeds and Data Streams source data across multiple independent aggregators, vendors, and authoritative entities. The table below summarizes sourcing models for each asset type.
+
+For more information about evaluating data quality, assessing liquidity and distribution risks, understanding single-source providers, and implementing risk mitigation strategies, see [Evaluating Data Sources and Risks](/data-feeds/selecting-data-feeds#evaluating-data-sources-and-risks).
+
+| Asset Type                  | Data Sourcing Info                                                                                                                                         |
+| --------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Crypto Price                | 3+ crypto price data aggregators and/or market data vendors using CEX and/or DEX data                                                                      |
+| Crypto State Price          | 3+ crypto price data aggregators and/or market data vendors using DEX pool state data                                                                      |
+| Forex                       | 3+ market data vendors                                                                                                                                     |
+| Precious Metals             | 3+ market data vendors                                                                                                                                     |
+| US Oil                      | 3+ market data vendors                                                                                                                                     |
+| US Equities                 | 3+ market data vendors                                                                                                                                     |
+| UK & Euro ETFs              | 2+ market data vendors using 15 minute delayed data                                                                                                        |
+| SmartData PoR (offchain)    | Sourced directly from custodian, fund administrator, auditor, security auditor, asset manager, regulated appraiser of assets, or regulator approved source |
+| SmartData PoR (cross chain) | On-chain data                                                                                                                                              |
+| SmartData NAV (offchain)    | Sourced directly from Fund Administrator or Asset Manager of the fund                                                                                      |
+| Exchange Rate Feeds         | On-chain data                                                                                                                                              |
+| Crypto MarketCap            | 3+ crypto price data aggregators and/or market data vendors                                                                                                |
+| Composite Index Feeds       | DON calculated index values from 3+ crypto price data aggregators and/or market data vendors                                                               |
+| Central Bank Rates Feeds    | Direct from Central Bank's API                                                                                                                             |
+| Crypto LWBA                 | 3+ crypto price data aggregators and/or market data vendors using CEX orderbook data to produce Liquidity Weight Bid/Ask and Mid values                    |
+| Crypto State Price          | 3+ crypto price data aggregators and/or market data vendors using DEX pool state data                                                                      |
+| Data Link Long Tail Crypto  | Single source from 1 crypto price data aggregator                                                                                                          |
+| Forex                       | 3+ market data vendors                                                                                                                                     |
+| Precious Metals             | 3+ market data vendors                                                                                                                                     |
+| US Equities                 | 3+ market data vendors                                                                                                                                     |
+
+<Aside type="note" title="Need more details?">
+  For additional information about data sourcing, please{" "}
+  <a href="https://chain.link/contact?ref_id=DataFeed">contact us</a>.
+</Aside>

src/content/data-feeds/feed-types.mdx

@@ -0,0 +1,31 @@
+---
+section: dataFeeds
+date: Last Modified
+title: "Feed Types"
+metadata:
+  title: "Chainlink Data Feeds: Feed Types Overview"
+  description: "Overview of Chainlink Data Feed types including Price, SmartData (MVR), SVR, Rate & Volatility, and L2 Sequencer Uptime status feeds."
+  keywords:
+    [
+      "Chainlink",
+      "Data Feeds",
+      "Feed Types",
+      "Price Feeds",
+      "SmartData",
+      "MVR",
+      "SVR",
+      "Volatility",
+      "Rates",
+      "L2 Sequencer",
+    ]
+---
+
+Chainlink Data Feeds provide multiple feed types for different onchain use cases.
+
+| Feed Type                                                   | Purpose                                                                                                                                                               |
+| ----------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| [Price Feeds](/data-feeds/price-feeds)                      | Aggregated, decentralized asset prices with cryptographic integrity for collateral, lending, and derivatives.                                                         |
+| [SmartData](/data-feeds/smartdata)                          | RWA-focused single-value and multi-variable (MVR) feeds (reserves, NAV, AUM, bundled OHLC sets) enabling secure, data-rich tokenization with efficient onchain reads. |
+| [Smart Value Recapture (SVR) Feeds](/data-feeds/svr-feeds)  | Specialized feeds providing metrics that help protocols recapture MEV or reduce external value leakage.                                                               |
+| [Rate and Volatility Feeds](/data-feeds/rates-feeds)        | Interest rate curves, staking APR, and realized volatility benchmarks used for pricing models, risk controls, and hedging strategies.                                 |
+| [L2 Sequencer Uptime Feeds](/data-feeds/l2-sequencer-feeds) | Real-time status of L2 sequencer availability for protective circuit breakers and fallback transaction logic.                                                         |