Skip to content

Data Feeds: SVR Updates - #4265

Open
dev-dist wants to merge 11 commits into
mainfrom
svr-expansion
Open

dev-dist wants to merge 11 commits into
mainfrom
svr-expansion

Conversation

@dev-dist

@dev-dist dev-dist commented Oct 2, 2026 •

Copy link
Copy Markdown
Collaborator

This pull request updates and expands the documentation and configuration for Chainlink SVR (Smart Value Recapture) Data Feeds, reflecting the broader availability of SVR on multiple networks beyond Ethereum Mainnet and improving clarity around protocol support, onboarding, and contract references. It also updates sidebar navigation and corrects contract addresses in code samples.

Key changes:

1. Documentation Expansion and Clarity

  • Updated all references to SVR availability to include new networks: Base, Arbitrum, BNB Chain, Monad, Arc, HyperEVM, Ink, Robinhood Chain, and Unichain, replacing previous references that only mentioned Base, Arbitrum, and BNB Chain. [1] [2] [3]
  • Improved the explanation of SVR feed variants, replacing the "SVR-Backup (Legacy)" section with clearer descriptions of "Compound SVR Feeds" and labeling feeds by protocol (Shared, Aave, Compound). [1] [2] [3] [4]
  • Expanded and clarified the list of supported protocols per network, using tables for recommended bond amounts and protocol support, and removed outdated or redundant sections.

2. Navigation and Sidebar Updates

  • Updated sidebar and "What's Next" navigation entries to use the more general "Atlas" onboarding guide, removing specific network mentions from titles. [1] [2]

3. Code and Contract Reference Corrections

  • Updated contract addresses for Atlas and DappControl in code samples and documentation to reflect current deployments. [1] [2] [3]
  • Refactored the onboarding guide to use a shared AtlasContractsTable component for displaying contract addresses, improving maintainability.

4. Onboarding Guide and Table Updates

  • Updated onboarding guides and tables to reflect the expanded set of supported networks and protocols, and to clarify the differences between Ethereum Mainnet (using Flashbots MEV-Share) and other networks (using Atlas). [1] [2] [3] [4]

These changes ensure the documentation is accurate, up-to-date, and easier for users to navigate and understand as Chainlink SVR expands to more networks and protocols.This pull request updates the Chainlink SVR (Smart Value Recapture) documentation and related configuration to reflect expanded network support, clarify feed variants, and improve contract reference information. The changes ensure the documentation accurately represents the current state of SVR support across multiple chains and enhances clarity for integrators and searchers.

Key changes include:

Expanded network support and onboarding references:

  • Updated all references to Atlas onboarding to remove specific chain names from titles and links, reflecting that Atlas now supports multiple networks beyond just Base, Arbitrum, BNB Chain, and Monad. The supported networks now include Arc, HyperEVM, Ink, Robinhood Chain, and Unichain. [1] [2] [3] [4] [5] [6]
  • Updated onboarding guides and sidebar configuration to use the generalized "Atlas" terminology. [1] [2]

Feed variant and documentation improvements:

  • Replaced references to legacy "SVR-Backup" feeds with new documentation for "Compound SVR Feeds" and clarified feed variant labeling throughout the documentation. [1] [2] [3] [4] [5] [6]
  • Clarified that each SVR feed is labeled with its variant, improving guidance for integrators on selecting the correct feed. [1] [2] [3] [4] [5]

Atlas contract and component references:

  • Consolidated and clarified the "Contract References" section, removing hardcoded contract address blocks from the MDX file and replacing them with a reusable AtlasContractsTable component. This makes contract references more maintainable and up-to-date. [1] [2] [3]
  • Updated contract addresses and dApp control addresses in code samples to reflect the latest deployments. [1] [2] [3]

General documentation clarity:

  • Improved language throughout the documentation to clarify network coverage, onboarding steps, and integration requirements for new and existing users. [1] [2] [3]

These updates ensure the documentation is accurate, easier to maintain, and provides clear guidance for all supported networks and feed variants.

@dev-dist
dev-dist requested review from a team as code owners October 2, 2026 19:44
@vercel

vercel Bot commented Oct 2, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
documentation Ready Ready Preview Nov 10, 2026 5:34pm UTC

Request Review

@github-actions

github-actions Bot commented Oct 2, 2026

Copy link
Copy Markdown
Contributor

👋 dev-dist, thanks for creating this pull request!

To help reviewers, please consider creating future PRs as drafts first. This allows you to self-review and make any final changes before notifying the team.

Once you're ready, you can mark it as "Ready for review" to request feedback. Thanks!

khadni
khadni previously approved these changes Nov 9, 2026

This branch was successfully deployed

1 active deployment
Preview — 25638113 Deployed Nov 10, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants