From ff96677ca0b9c7b02a66b5d0637fd107e64db6ac Mon Sep 17 00:00:00 2001 From: Sebastian Lerner Date: Tue, 25 Aug 2026 21:41:39 +0100 Subject: [PATCH 1/6] Simplify and generalize Default SVR Activation copy - Drop the Base-specific network/feed list since default activation also applies on Ink; keep the language network-agnostic. - Replace "may be activated" / "from day one" with clearer phrasing. - Note that default-activated feeds are listed as SVR Proxy 2 on the Feed Addresses page and data.chain.link, and are functionally identical to SVR Proxy. --- src/content/data-feeds/svr-feeds/index.mdx | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/src/content/data-feeds/svr-feeds/index.mdx b/src/content/data-feeds/svr-feeds/index.mdx index f0a6ed5b2d6..f88b78b9f5e 100644 --- a/src/content/data-feeds/svr-feeds/index.mdx +++ b/src/content/data-feeds/svr-feeds/index.mdx @@ -172,11 +172,13 @@ Aave SVR feeds are specifically tailored for the Aave protocol and are only inte ## Default SVR Activation -In coordination with blockchain ecosystem partners, Chainlink SVR may be activated by default for BTC, ETH, XRP, SOL, DOGE, LTC, and ADA Data Feeds on Base. Where SVR is active by default, new and existing lending market deployments will recapture oracle-related MEV (OEV) through the SVR flow from day one without additional integration work. +Chainlink SVR is activated by default for all Chainlink Data Feeds live on certain blockchain networks. Where SVR is active by default, new and existing lending market deployments recapture oracle-related MEV (OEV) without any additional integration work. -Teams deploying applications that use these feeds on networks where SVR is active by default should contact [chainlink_data_feeds@smartcontract.com](mailto:chainlink_data_feeds@smartcontract.com), as recaptured OEV is shared with integrating DeFi protocols as described in [Economics and Revenue Split](#economics-and-revenue-split). +Integrators should expect zero service disruption during activation, and no action is needed on their part. -Protocols that prefer not to use SVR can opt out at any time by reading from the "Standard" proxy that complements every SVR proxy for the relevant feed. +On these networks, SVR feeds are listed as **SVR Proxy 2** on the [Feed Addresses](/data-feeds/price-feeds/addresses) page and on [data.chain.link](https://data.chain.link/). SVR Proxy and SVR Proxy 2 are functionally identical. + +For any questions, contact [chainlink_data_feeds@smartcontract.com](mailto:chainlink_data_feeds@smartcontract.com). Protocols can also opt out at any time by reading from the "Standard" proxy that complements every SVR proxy for the relevant feed. ## How Protocols Can Utilize SVR Feeds From ecc5047a2a89af5f5c7ac6a8be9dbb1022ddc4d7 Mon Sep 17 00:00:00 2001 From: Sebastian Lerner Date: Tue, 25 Aug 2026 22:16:57 +0100 Subject: [PATCH 2/6] Clarify that default SVR activation applies to certain feeds, not all The prior wording implied every feed on a given network gets SVR by default; only certain feeds do. --- src/content/data-feeds/svr-feeds/index.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/data-feeds/svr-feeds/index.mdx b/src/content/data-feeds/svr-feeds/index.mdx index f88b78b9f5e..73479d72805 100644 --- a/src/content/data-feeds/svr-feeds/index.mdx +++ b/src/content/data-feeds/svr-feeds/index.mdx @@ -172,7 +172,7 @@ Aave SVR feeds are specifically tailored for the Aave protocol and are only inte ## Default SVR Activation -Chainlink SVR is activated by default for all Chainlink Data Feeds live on certain blockchain networks. Where SVR is active by default, new and existing lending market deployments recapture oracle-related MEV (OEV) without any additional integration work. +Chainlink SVR is activated by default for certain Chainlink Data Feeds on certain blockchain networks. Where SVR is active by default, new and existing lending market deployments recapture oracle-related MEV (OEV) without any additional integration work. Integrators should expect zero service disruption during activation, and no action is needed on their part. From 4314104bc9ce68ec01a5dafaac77a8ea37a37845 Mon Sep 17 00:00:00 2001 From: Sebastian Lerner Date: Tue, 25 Aug 2026 22:17:52 +0100 Subject: [PATCH 3/6] Drop redundant MEV expansion when referring to OEV OEV and MEV are already defined earlier on the page. --- src/content/data-feeds/svr-feeds/index.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/data-feeds/svr-feeds/index.mdx b/src/content/data-feeds/svr-feeds/index.mdx index 73479d72805..51188690569 100644 --- a/src/content/data-feeds/svr-feeds/index.mdx +++ b/src/content/data-feeds/svr-feeds/index.mdx @@ -172,7 +172,7 @@ Aave SVR feeds are specifically tailored for the Aave protocol and are only inte ## Default SVR Activation -Chainlink SVR is activated by default for certain Chainlink Data Feeds on certain blockchain networks. Where SVR is active by default, new and existing lending market deployments recapture oracle-related MEV (OEV) without any additional integration work. +Chainlink SVR is activated by default for certain Chainlink Data Feeds on certain blockchain networks. Where SVR is active by default, new and existing lending market deployments recapture OEV without any additional integration work. Integrators should expect zero service disruption during activation, and no action is needed on their part. From 8b9003f8cdf461c70e5d3321e83264580ca2a9bf Mon Sep 17 00:00:00 2001 From: Sebastian Lerner Date: Tue, 25 Aug 2026 22:18:51 +0100 Subject: [PATCH 4/6] Use "when SVR is enabled" to describe the activation moment "Where...is active" read as a static state; "when...is enabled" better captures the transition being described. --- src/content/data-feeds/svr-feeds/index.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/data-feeds/svr-feeds/index.mdx b/src/content/data-feeds/svr-feeds/index.mdx index 51188690569..b47c318128c 100644 --- a/src/content/data-feeds/svr-feeds/index.mdx +++ b/src/content/data-feeds/svr-feeds/index.mdx @@ -172,7 +172,7 @@ Aave SVR feeds are specifically tailored for the Aave protocol and are only inte ## Default SVR Activation -Chainlink SVR is activated by default for certain Chainlink Data Feeds on certain blockchain networks. Where SVR is active by default, new and existing lending market deployments recapture OEV without any additional integration work. +Chainlink SVR is activated by default for certain Chainlink Data Feeds on certain blockchain networks. When SVR is enabled by default, new and existing lending market deployments recapture OEV without any additional integration work. Integrators should expect zero service disruption during activation, and no action is needed on their part. From 5ea1c4f365d75ff6fcb2ff480bbd3f2bfe702822 Mon Sep 17 00:00:00 2001 From: Sebastian Lerner Date: Wed, 26 Aug 2026 12:45:12 +0100 Subject: [PATCH 5/6] Name Base and Ink as the currently supported default-activation networks --- src/content/data-feeds/svr-feeds/index.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/data-feeds/svr-feeds/index.mdx b/src/content/data-feeds/svr-feeds/index.mdx index b47c318128c..81457528c9e 100644 --- a/src/content/data-feeds/svr-feeds/index.mdx +++ b/src/content/data-feeds/svr-feeds/index.mdx @@ -172,7 +172,7 @@ Aave SVR feeds are specifically tailored for the Aave protocol and are only inte ## Default SVR Activation -Chainlink SVR is activated by default for certain Chainlink Data Feeds on certain blockchain networks. When SVR is enabled by default, new and existing lending market deployments recapture OEV without any additional integration work. +Chainlink SVR is activated by default for certain Chainlink Data Feeds on certain blockchain networks, currently Base and Ink. When SVR is enabled by default, new and existing lending market deployments recapture OEV without any additional integration work. Integrators should expect zero service disruption during activation, and no action is needed on their part. From f8463a4232a5b1942788cfdcf909baa4dc9aa664 Mon Sep 17 00:00:00 2001 From: devin distefano Date: Fri, 28 Aug 2026 12:19:16 -0500 Subject: [PATCH 6/6] update language to match deployed version --- src/content/data-feeds/llms-full.txt | 63 ++-------------------- src/content/data-feeds/svr-feeds/index.mdx | 63 +--------------------- 2 files changed, 7 insertions(+), 119 deletions(-) diff --git a/src/content/data-feeds/llms-full.txt b/src/content/data-feeds/llms-full.txt index 43a8342187e..c765170f2f1 100644 --- a/src/content/data-feeds/llms-full.txt +++ b/src/content/data-feeds/llms-full.txt @@ -5444,61 +5444,6 @@ make ma-set-latest-round NETWORK=devnet && make ac-set-answer NETWORK=devnet && # Smart Value Recapture (SVR) Feeds Source: https://docs.chain.link/data-feeds/svr-feeds -export async function getFeeds() { - const ethereumMainnet = CHAINS.find((chain) => chain.page === "ethereum")?.networks.find( - (network) => network.networkType === "mainnet" - ) - -const rddUrl = ethereumMainnet?.rddUrl - -if (!rddUrl) { -return [] -} - -try { -const response = await fetch(rddUrl) -const data = await response.json() - - // Find all feeds that have SVR variants and are not hidden - const svrFeeds = data.filter( - (feed) => feed.secondaryProxyAddress && !feed.docs?.hidden - ) - - // Group feeds by their base name (e.g., "BTC/USD", "ETH/USD") - const feedGroups = {} - - svrFeeds.forEach(feed => { - const baseName = feed.name.replace(" / ", "/") - - if (!feedGroups[baseName]) { - feedGroups[baseName] = { - name: baseName, - aaveAddress: null, - svrAddress: null, - svrBackupAddress: null, - } - } - - if (isAaveSVR(feed)) { - feedGroups[baseName].aaveAddress = feed.contractAddress - } else if (isNewSharedSVR(feed)) { - feedGroups[baseName].svrAddress = feed.contractAddress - } else if (isSharedSVR(feed)) { - feedGroups[baseName].svrBackupAddress = feed.contractAddress - } - }) - - // Convert to array and sort - const combinedFeeds = Object.values(feedGroups) - .sort((a, b) => a.name.localeCompare(b.name)) - - return combinedFeeds - -} catch (error) { -return [] -} -} -