Repository navigation
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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! |
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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:
Feed variant and documentation improvements:
Atlas contract and component references:
AtlasContractsTablecomponent. This makes contract references more maintainable and up-to-date. [1] [2] [3]General documentation clarity:
These updates ensure the documentation is accurate, easier to maintain, and provides clear guidance for all supported networks and feed variants.