Skip to content

docs: generalize Default SVR Activation copy, add SVR Proxy 2 naming #4105

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
dev-dist merged 7 commits into from
Aug 28, 2026
+11 −121
Merged

docs: generalize Default SVR Activation copy, add SVR Proxy 2 naming #4105

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
7 commits
Select commit Hold shift + click to select a range
ff96677
Simplify and generalize Default SVR Activation copy
Aug 25, 2026
ecc5047
Clarify that default SVR activation applies to certain feeds, not all
Aug 25, 2026
4314104
Drop redundant MEV expansion when referring to OEV
Aug 25, 2026
8b9003f
Use "when SVR is enabled" to describe the activation moment
Aug 25, 2026
5ea1c4f
Name Base and Ink as the currently supported default-activation networks
Aug 26, 2026
6c63c1b
Merge branch 'main' into svr-default-activation-copy-tweaks
dev-dist Aug 27, 2026
f8463a4
update language to match deployed version
dev-dist Aug 28, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
63 changes: 5 additions & 58 deletions src/content/data-feeds/llms-full.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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 []
}
}

<Aside type="note" title="SVR integrated with Titan OFA">
<p>
SVR now supports multiple orderflow auctions in parallel on Ethereum mainnet, including Flashbots and Titan.
Expand Down Expand Up @@ -5592,11 +5537,13 @@ Legacy shared SVR feeds that are still actively used by existing applications. S

## 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 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.

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).
On these networks, SVR feeds have an **SVR** label on the [Feed Addresses](/data-feeds/price-feeds/addresses?network=base\&showSvr=true) page and on [data.chain.link](https://data.chain.link/). Previously deployed SVR feeds remain available and function as expected, and can be identified with the **SVR-Backup** label.

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.
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

Expand Down
69 changes: 6 additions & 63 deletions src/content/data-feeds/svr-feeds/index.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,66 +13,7 @@ whatsnext:
}
---

import { Aside, ClickToZoom, CopyText } from "@components"
import { CHAINS } from "@features/data/chains"
import { isSharedSVR, isAaveSVR, isNewSharedSVR } from "~/features/feeds/utils/svrDetection.ts"

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 []
}
}

export const feeds = await getFeeds()
import { Aside, ClickToZoom } from "@components"

<Aside type="note" title="SVR integrated with Titan OFA">
<p>
Expand Down Expand Up @@ -183,11 +124,13 @@ Legacy shared SVR feeds that are still actively used by existing applications. S

## 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 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.

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).
On these networks, SVR feeds have an **SVR** label on the [Feed Addresses](/data-feeds/price-feeds/addresses?network=base&showSvr=true) page and on [data.chain.link](https://data.chain.link/). Previously deployed SVR feeds remain available and function as expected, and can be identified with the **SVR-Backup** label.

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.
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

Expand Down
Loading