docs: update BNB Chain oracle config — add Atlas (VIP-628)#354
Draft
Venus-ZD wants to merge 2 commits into
Draft
docs: update BNB Chain oracle config — add Atlas (VIP-628)#354Venus-ZD wants to merge 2 commits into
Venus-ZD wants to merge 2 commits into
Conversation
…ance to Atlas migration
|
GitBook Preview: https://docs-v4.venus.io/~/revisions/9gL4ep0VrvYZsiClc0eR/ |
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.
Summary
Updates the BNB Chain oracle configuration table on the Resilient Price Oracle page to reflect the current on-chain state (verified 2026-06-15 via
ResilientOracle.getTokenConfig). The page had not been updated since the VIP-628 Atlas rollout.Changes
0x9E6928Ec418948ceb9f1cd9872fD312b13D841D0). Binance Oracle now remains only on asBNB (pivot) and VAI in BSC Core.@venusprotocol/oracledeployments).33 rows updated.
Verification
All rows cross-checked against on-chain
getTokenConfigand the internal Oracle Mastersheet — 0 provider mismatches. Previously-flagged items now confirmed:SolvBTCOneJumpChainlinkOracle/SolvBTCOneJumpFundamentalOracle/SolvBTCOneJumpRedStoneOracle).Out of scope