Skip to content

Commit 56f70d2

Browse files
dev-distdev-dist
authored
Data: Batch of quality, sourcing, and usage updates (#3225)
* weekend usage disclaimer for v10 * data sourcing notes * data sourcing improvement * df sidebar cleanup * formatting * data feeds data sourcing * another backlink * market hours callout * llmgen
1 parent 6caeb28 commit 56f70d2

File tree

13 files changed

+16510
-16220
lines changed

13 files changed

+16510
-16220
lines changed

‎reports/llms-report.json‎

Lines changed: 11 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
{
2-
"startedAt": "2025-11-24T20:57:41.455Z",
2+
"startedAt": "2025-11-25T23:16:10.318Z",
33
"siteBase": "https://docs.chain.link",
44
"sections": [
55
{
@@ -30,25 +30,25 @@
3030
"section": "ccip",
3131
"pagesProcessed": 260,
3232
"outputPath": "src/content/ccip/llms-full.txt",
33-
"bytes": 2847128,
34-
"prevBytes": 2847128,
33+
"bytes": 2849278,
34+
"prevBytes": 2849278,
3535
"deltaBytes": 0
3636
},
3737
{
3838
"section": "data-feeds",
39-
"pagesProcessed": 35,
39+
"pagesProcessed": 37,
4040
"outputPath": "src/content/data-feeds/llms-full.txt",
41-
"bytes": 291525,
42-
"prevBytes": 291525,
41+
"bytes": 302350,
42+
"prevBytes": 302350,
4343
"deltaBytes": 0
4444
},
4545
{
4646
"section": "data-streams",
47-
"pagesProcessed": 53,
47+
"pagesProcessed": 54,
4848
"outputPath": "src/content/data-streams/llms-full.txt",
49-
"bytes": 474463,
50-
"prevBytes": 474592,
51-
"deltaBytes": -129
49+
"bytes": 477065,
50+
"prevBytes": 477061,
51+
"deltaBytes": 4
5252
},
5353
{
5454
"section": "dta-technical-standard",
@@ -123,5 +123,5 @@
123123
"deltaBytes": 0
124124
}
125125
],
126-
"finishedAt": "2025-11-24T20:57:45.128Z"
126+
"finishedAt": "2025-11-25T23:16:13.816Z"
127127
}

‎src/config/sidebar.ts‎

Lines changed: 17 additions & 20 deletions
Original file line numberDiff line numberDiff line change
@@ -545,35 +545,28 @@ export const SIDEBAR: Partial<Record<Sections, SectionEntry[]>> = {
545545
url: "data-feeds/developer-responsibilities",
546546
},
547547
{
548-
title: "Price Feeds",
549-
url: "data-feeds/price-feeds",
550-
},
551-
{
552-
title: "SmartData",
553-
url: "data-feeds/smartdata",
548+
title: "Feed Types",
549+
url: "data-feeds/feed-types",
554550
children: [
551+
{ title: "Price Feeds", url: "data-feeds/price-feeds" },
555552
{
556-
title: "Multiple-Variable Response (MVR) Feeds",
557-
url: "data-feeds/mvr-feeds",
553+
title: "SmartData",
554+
url: "data-feeds/smartdata",
555+
children: [{ title: "Multiple-Variable Response (MVR) Feeds", url: "data-feeds/mvr-feeds" }],
558556
},
557+
{ title: "Smart Value Recapture (SVR) Feeds", url: "data-feeds/svr-feeds" },
558+
{ title: "Rate and Volatility Feeds", url: "data-feeds/rates-feeds" },
559+
{ title: "L2 Sequencer Uptime Feeds", url: "data-feeds/l2-sequencer-feeds" },
559560
],
560561
},
561-
{
562-
title: "Smart Value Recapture (SVR) Feeds",
563-
url: "data-feeds/svr-feeds",
564-
},
565-
{
566-
title: "Rate and Volatility Feeds",
567-
url: "data-feeds/rates-feeds",
568-
},
569-
{
570-
title: "L2 Sequencer Uptime Feeds",
571-
url: "data-feeds/l2-sequencer-feeds",
572-
},
573562
{
574563
title: "Flags Contract Registry",
575564
url: "data-feeds/contract-registry",
576565
},
566+
{
567+
title: "Data Sources",
568+
url: "data-feeds/data-sources",
569+
},
577570
{
578571
title: "Release Notes",
579572
url: "https://dev.chain.link/changelog?product=Data+Feeds",
@@ -823,6 +816,10 @@ export const SIDEBAR: Partial<Record<Sections, SectionEntry[]>> = {
823816
title: "Billing",
824817
url: "data-streams/billing",
825818
},
819+
{
820+
title: "Data Sources",
821+
url: "data-streams/data-sources",
822+
},
826823
{
827824
title: "Release Notes",
828825
url: "https://dev.chain.link/changelog?product=Data+Streams",

‎src/content/ccip/llms-full.txt‎

Lines changed: 16202 additions & 16155 deletions
Large diffs are not rendered by default.

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

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -7712,7 +7712,7 @@ The `prepareScenario()` function is invoked at the beginning of each test case.
77127712
sourceCCIPBnMToken.approve(address(sourceRouter), amountToSend);
77137713
```
77147714

7715-
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
7715+
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
77167716
are returned by the `prepareScenario()` function for use in the calling test case:
77177717

77187718
```solidity
@@ -7759,7 +7759,7 @@ Here are the steps involved in this test case:
77597759
ccipLocalSimulatorFork.requestLinkFromFaucet(alice, 10 ether);
77607760
```
77617761

7762-
5. Construct the [Client.EVM2AnyMessage](/ccip/api-reference/evm/v1.6.2/client#evm2anymessage) structure with the receiver, token amounts, and other necessary details.
7762+
5. Construct the [Client.EVM2AnyMessage](/ccip/api-reference/evm/v1.6.1/client#evm2anymessage) structure with the receiver, token amounts, and other necessary details.
77637763

77647764
- Set the `data` parameter to an empty string because you are not sending any arbitrary data, only tokens.
77657765
- 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:
78327832
deal(alice, 5 ether);
78337833
```
78347834

7835-
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.
7835+
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.
78367836
The main difference is that the `feeToken` is set with `address(0)` to indicate that the fees are paid in native gas:
78377837

78387838
```solidity
@@ -7993,7 +7993,7 @@ The `prepareScenario()` function is invoked at the beginning of each test case.
79937993
ccipBnMToken.approve(address(router), amountToSend);
79947994
```
79957995

7996-
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:
7996+
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:
79977997

79987998
```solidity
79997999
tokensToSendDetails = new Client.EVMTokenAmount[](1);
@@ -8032,7 +8032,7 @@ Here are the steps involved in this test case:
80328032
ccipLocalSimulator.requestLinkFromFaucet(alice, 5 ether);
80338033
```
80348034

8035-
5. Construct the [Client.EVM2AnyMessage](/ccip/api-reference/evm/v1.6.2/client#evm2anymessage) structure with the receiver, token amounts, and other necessary details.
8035+
5. Construct the [Client.EVM2AnyMessage](/ccip/api-reference/evm/v1.6.1/client#evm2anymessage) structure with the receiver, token amounts, and other necessary details.
80368036

80378037
- Set the `data` parameter to an empty string because you are not sending any arbitrary data, only tokens.
80388038
- 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:
80968096
deal(alice, 5 ether);
80978097
```
80988098

8099-
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.
8099+
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.
81008100
The main difference is that the `feeToken` is set with `address(0)` to indicate that the fees are paid in native gas:
81018101

81028102
```solidity
@@ -8429,7 +8429,7 @@ while paying fees in LINK. Here are the steps involved in this test case:
84298429
]
84308430
```
84318431

8432-
6. Construct the [Client.EVM2AnyMessage](/ccip/api-reference/evm/v1.6.2/client#evm2anymessage) structure with the receiver, token amounts, and other necessary details.
8432+
6. Construct the [Client.EVM2AnyMessage](/ccip/api-reference/evm/v1.6.1/client#evm2anymessage) structure with the receiver, token amounts, and other necessary details.
84338433

84348434
- Use an empty string for the `data` parameter because you are not sending any arbitrary data (only tokens).
84358435
- 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‎

Lines changed: 65 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,65 @@
1+
---
2+
section: dataFeeds
3+
date: Last Modified
4+
title: "Data Sources"
5+
metadata:
6+
title: "Data Sources | Chainlink Data Feeds"
7+
description: "Reference overview of data sourcing for Chainlink Data Feeds asset and product types."
8+
keywords:
9+
[
10+
"Data Sources",
11+
"Data Feeds",
12+
"Data Streams",
13+
"Crypto Price",
14+
"Crypto State Price",
15+
"Forex",
16+
"Precious Metals",
17+
"US Oil",
18+
"US Equities",
19+
"UK ETFs",
20+
"Euro ETFs",
21+
"Proof of Reserve",
22+
"Cross Chain PoR",
23+
"NAV",
24+
"Exchange Rate",
25+
"MarketCap",
26+
"Composite Index",
27+
"Central Bank Rates",
28+
"Crypto LWBA",
29+
"Data Link Long Tail Crypto",
30+
]
31+
---
32+
33+
import Aside from "@components/Aside.astro"
34+
35+
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.
36+
37+
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).
38+
39+
| Asset Type | Data Sourcing Info |
40+
| --------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |
41+
| Crypto Price | 3+ crypto price data aggregators and/or market data vendors using CEX and/or DEX data |
42+
| Crypto State Price | 3+ crypto price data aggregators and/or market data vendors using DEX pool state data |
43+
| Forex | 3+ market data vendors |
44+
| Precious Metals | 3+ market data vendors |
45+
| US Oil | 3+ market data vendors |
46+
| US Equities | 3+ market data vendors |
47+
| UK & Euro ETFs | 2+ market data vendors using 15 minute delayed data |
48+
| SmartData PoR (offchain) | Sourced directly from custodian, fund administrator, auditor, security auditor, asset manager, regulated appraiser of assets, or regulator approved source |
49+
| SmartData PoR (cross chain) | On-chain data |
50+
| SmartData NAV (offchain) | Sourced directly from Fund Administrator or Asset Manager of the fund |
51+
| Exchange Rate Feeds | On-chain data |
52+
| Crypto MarketCap | 3+ crypto price data aggregators and/or market data vendors |
53+
| Composite Index Feeds | DON calculated index values from 3+ crypto price data aggregators and/or market data vendors |
54+
| Central Bank Rates Feeds | Direct from Central Bank's API |
55+
| 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 |
56+
| Crypto State Price | 3+ crypto price data aggregators and/or market data vendors using DEX pool state data |
57+
| Data Link Long Tail Crypto | Single source from 1 crypto price data aggregator |
58+
| Forex | 3+ market data vendors |
59+
| Precious Metals | 3+ market data vendors |
60+
| US Equities | 3+ market data vendors |
61+
62+
<Aside type="note" title="Need more details?">
63+
For additional information about data sourcing, please{" "}
64+
<a href="https://chain.link/contact?ref_id=DataFeed">contact us</a>.
65+
</Aside>

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

Lines changed: 31 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,31 @@
1+
---
2+
section: dataFeeds
3+
date: Last Modified
4+
title: "Feed Types"
5+
metadata:
6+
title: "Chainlink Data Feeds: Feed Types Overview"
7+
description: "Overview of Chainlink Data Feed types including Price, SmartData (MVR), SVR, Rate & Volatility, and L2 Sequencer Uptime status feeds."
8+
keywords:
9+
[
10+
"Chainlink",
11+
"Data Feeds",
12+
"Feed Types",
13+
"Price Feeds",
14+
"SmartData",
15+
"MVR",
16+
"SVR",
17+
"Volatility",
18+
"Rates",
19+
"L2 Sequencer",
20+
]
21+
---
22+
23+
Chainlink Data Feeds provide multiple feed types for different onchain use cases.
24+
25+
| Feed Type | Purpose |
26+
| ----------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
27+
| [Price Feeds](/data-feeds/price-feeds) | Aggregated, decentralized asset prices with cryptographic integrity for collateral, lending, and derivatives. |
28+
| [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. |
29+
| [Smart Value Recapture (SVR) Feeds](/data-feeds/svr-feeds) | Specialized feeds providing metrics that help protocols recapture MEV or reduce external value leakage. |
30+
| [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. |
31+
| [L2 Sequencer Uptime Feeds](/data-feeds/l2-sequencer-feeds) | Real-time status of L2 sequencer availability for protective circuit breakers and fallback transaction logic. |

0 commit comments

Comments
 (0)