You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: public/changelog.json
+7Lines changed: 7 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -398,6 +398,13 @@
398
398
}
399
399
},
400
400
"data": [
401
+
{
402
+
"category": "release",
403
+
"date": "2026-03-27",
404
+
"description": "Self-managed Data Feeds are now supported, allowing chains and operators to publish data onchain. See [Self-Managed Feeds](/data-feeds/self-managed-feeds) for more information, or contact the Data Feeds team at [chainlink_data_feeds@smartcontract.com](mailto:chainlink_data_feeds@smartcontract.com) for details regarding deployment. \n \n _Note: Chainlink Labs does not manage the onchain publication path, monitoring, or service levels for self-managed feeds and does not list their proxy addresses in official documentation; the chain or its operator is responsible for running the workflow, maintaining contracts, and supporting integrators._",
Copy file name to clipboardExpand all lines: src/content/data-feeds/feed-types.mdx
+10-8Lines changed: 10 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ date: Last Modified
4
4
title: "Feed Types"
5
5
metadata:
6
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."
7
+
description: "Overview of Chainlink Data Feed types including Price, SmartData (MVR), SVR, Rate & Volatility, L2 Sequencer Uptime status feeds, and Self-Managed Feeds."
8
8
keywords:
9
9
[
10
10
"Chainlink",
@@ -17,15 +17,17 @@ metadata:
17
17
"Volatility",
18
18
"Rates",
19
19
"L2 Sequencer",
20
+
"Self-Managed Feeds",
20
21
]
21
22
---
22
23
23
24
Chainlink Data Feeds provide multiple feed types for different onchain use cases.
|[Price Feeds](/data-feeds/price-feeds)| Aggregated, decentralized asset prices with cryptographic integrity for collateral, lending, and derivatives. |
|[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. |
|[Price Feeds](/data-feeds/price-feeds)| Aggregated, decentralized asset prices with cryptographic integrity for collateral, lending, and derivatives. |
|[Smart Value Recapture (SVR) Feeds](/data-feeds/svr-feeds)| Specialized feeds providing metrics that help protocols recapture MEV or reduce external value leakage. |
31
+
|[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. |
32
+
|[L2 Sequencer Uptime Feeds](/data-feeds/l2-sequencer-feeds)| Real-time status of L2 sequencer availability for protective circuit breakers and fallback transaction logic. |
33
+
|[Self-Managed Feeds](/data-feeds/self-managed-feeds)| Data Feeds where a chain or third party publishes onchain updates instead of Chainlink Labs–managed oracle infrastructure; not operated or monitored by Chainlink Labs. |
@@ -85,6 +86,12 @@ L2 sequencer feeds track the last known status of the sequencer on an L2 network
85
86
86
87
To learn how to use L2 sequencer uptime feeds, see the [L2 Sequencer Uptime Feeds](/data-feeds/l2-sequencer-feeds) documentation.
87
88
89
+
### Self-managed feeds
90
+
91
+
Some networks publish Data Feed–style proxy contracts where **onchain updates are written by the chain or a third-party operator** (for example using a CRE workflow that reads [Chainlink Data Streams](/data-streams)), rather than through Chainlink Labs–managed decentralized oracle networks. **Chainlink Labs does not operate, monitor, or list addresses** for these deployments in official feed catalogs.
92
+
93
+
For responsibilities, monitoring scope, and how to obtain contract addresses, see [Self-Managed Feeds](/data-feeds/self-managed-feeds).
94
+
88
95
## Components of a data feed
89
96
90
97
Data Feeds are examples of decentralized oracle networks with different interfaces depending on the type of data they provide. Each feed type includes specific components:
| [Smart Value Recapture (SVR) Feeds](/data-feeds/svr-feeds) | Specialized feeds providing metrics that help protocols recapture MEV or reduce external value leakage. |
1058
-
| [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. |
1059
-
| [L2 Sequencer Uptime Feeds](/data-feeds/l2-sequencer-feeds) | Real-time status of L2 sequencer availability for protective circuit breakers and fallback transaction logic. |
| [Smart Value Recapture (SVR) Feeds](/data-feeds/svr-feeds) | Specialized feeds providing metrics that help protocols recapture MEV or reduce external value leakage. |
1058
+
| [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. |
1059
+
| [L2 Sequencer Uptime Feeds](/data-feeds/l2-sequencer-feeds) | Real-time status of L2 sequencer availability for protective circuit breakers and fallback transaction logic. |
1060
+
| [Self-Managed Feeds](/data-feeds/self-managed-feeds) | Data Feeds where a chain or third party publishes onchain updates instead of Chainlink Labs–managed oracle infrastructure; not operated or monitored by Chainlink Labs. |
1060
1061
1061
1062
---
1062
1063
@@ -1469,6 +1470,7 @@ Data feeds provide many different types of data for your applications.
1469
1470
- [Smart Value Recapture (SVR) Feeds](#smart-value-recapture-svr-feeds)
1470
1471
- [Rate and Volatility Feeds](#rate-and-volatility-feeds)
@@ -1515,6 +1517,12 @@ L2 sequencer feeds track the last known status of the sequencer on an L2 network
1515
1517
1516
1518
To learn how to use L2 sequencer uptime feeds, see the [L2 Sequencer Uptime Feeds](/data-feeds/l2-sequencer-feeds) documentation.
1517
1519
1520
+
### Self-managed feeds
1521
+
1522
+
Some networks publish Data Feed–style proxy contracts where **onchain updates are written by the chain or a third-party operator** (for example using a CRE workflow that reads [Chainlink Data Streams](/data-streams)), rather than through Chainlink Labs–managed decentralized oracle networks. **Chainlink Labs does not operate, monitor, or list addresses** for these deployments in official feed catalogs.
1523
+
1524
+
For responsibilities, monitoring scope, and how to obtain contract addresses, see [Self-Managed Feeds](/data-feeds/self-managed-feeds).
1525
+
1518
1526
## Components of a data feed
1519
1527
1520
1528
Data Feeds are examples of decentralized oracle networks with different interfaces depending on the type of data they provide. Each feed type includes specific components:
@@ -3901,6 +3909,50 @@ When you use Data Feeds for ETFs or Foreign Exchange (Forex) data, be aware of t
**Self-managed feeds** are Data Feeds where values are written onchain by a **third party** (typically the chain or its designated operator), not by Chainlink node operators publishing through Chainlink Labs–managed oracle infrastructure.
3921
+
3922
+
At a high level, a [Chainlink Runtime Environment (CRE)](/cre) workflow reads from [Chainlink Data Streams](/data-streams) and writes updates to a proxy contract so consumers can read answers using the same familiar Data Feeds interfaces. **Chainlink Labs does not manage the onchain publication path, monitoring, or service levels** for these deployments. The chain (or its operator) is responsible for running the workflow, maintaining contracts, and supporting integrators.
3923
+
3924
+
As of March 2026, **[Jovay](https://jovay.io/)** and **[Pharos](https://www.pharos.xyz/)** offer self-managed feed deployments. **Contract addresses for these feeds are not listed in Chainlink public documentation**; obtain deployed proxy addresses directly from those networks or their operators:
3925
+
3926
+
- [Jovay](https://jovay.io/)
3927
+
- [Pharos](https://www.pharos.xyz/)
3928
+
3929
+
## Responsibilities & guarantees
3930
+
3931
+
### Data quality
3932
+
3933
+
Data for assets are delivered through **[Chainlink Data Streams](/data-streams)**. Data Streams provides the offchain data for the self-managed feeds; however, it is the third party’s obligation to read, transform, or write the correct values onchain on schedule.
3934
+
3935
+
### Monitoring & service levels
3936
+
3937
+
**These onchain feeds are not managed or monitored by Chainlink Labs.**
3938
+
3939
+
Specifically:
3940
+
3941
+
- Chainlink Labs does **not** provide monitoring for:
3942
+
- Heartbeat compliance
3943
+
- Deviation compliance
3944
+
- End-to-end latency of writing prices onchain
3945
+
- Whether the correct data was written onchain
3946
+
- No service level agreements (SLAs) are provided for self-managed feed publication.
3947
+
- No onchain monitoring specific to these feeds is provided by Chainlink Labs.
3948
+
3949
+
### Feed visibility
3950
+
3951
+
- Proxy addresses for self-managed feeds **do not appear** on official Chainlink public documentation sites (including feed address catalogs).
3952
+
- Integrators must obtain deployed contract addresses **directly from the operators** of the self-managed feeds on each chain.
description: "Self-managed Data Feeds use Chainlink Data Streams as a data source while a third party publishes updates onchain. Chainlink Labs does not operate or monitor these feeds."
**Self-managed feeds** are Data Feeds where values are written onchain by a **third party** (typically the chain or its designated operator), not by Chainlink node operators publishing through Chainlink Labs–managed oracle infrastructure.
19
+
20
+
At a high level, a [Chainlink Runtime Environment (CRE)](/cre) workflow reads from [Chainlink Data Streams](/data-streams) and writes updates to a proxy contract so consumers can read answers using the same familiar Data Feeds interfaces. **Chainlink Labs does not manage the onchain publication path, monitoring, or service levels** for these deployments. The chain (or its operator) is responsible for running the workflow, maintaining contracts, and supporting integrators.
21
+
22
+
As of March 2026, **[Jovay](https://jovay.io/)** and **[Pharos](https://www.pharos.xyz/)** offer self-managed feed deployments. **Contract addresses for these feeds are not listed in Chainlink public documentation**; obtain deployed proxy addresses directly from those networks or their operators:
23
+
24
+
-[Jovay](https://jovay.io/)
25
+
-[Pharos](https://www.pharos.xyz/)
26
+
27
+
## Responsibilities & guarantees
28
+
29
+
### Data quality
30
+
31
+
Data for assets are delivered through **[Chainlink Data Streams](/data-streams)**. Data Streams provides the offchain data for the self-managed feeds; however, it is the third party’s obligation to read, transform, or write the correct values onchain on schedule.
32
+
33
+
### Monitoring & service levels
34
+
35
+
**These onchain feeds are not managed or monitored by Chainlink Labs.**
36
+
37
+
Specifically:
38
+
39
+
- Chainlink Labs does **not** provide monitoring for:
40
+
- Heartbeat compliance
41
+
- Deviation compliance
42
+
- End-to-end latency of writing prices onchain
43
+
- Whether the correct data was written onchain
44
+
- No service level agreements (SLAs) are provided for self-managed feed publication.
45
+
- No onchain monitoring specific to these feeds is provided by Chainlink Labs.
46
+
47
+
### Feed visibility
48
+
49
+
- Proxy addresses for self-managed feeds **do not appear** on official Chainlink public documentation sites (including feed address catalogs).
50
+
- Integrators must obtain deployed contract addresses **directly from the operators** of the self-managed feeds on each chain.
0 commit comments