Fix chainlist 314169 - #3094
Open
youngdev-eed wants to merge 3 commits into
Open
Conversation
Define101
reviewed
Aug 28, 2026
| @@ -0,0 +1,30 @@ | |||
| { | |||
Member
There was a problem hiding this comment.
export const data = {
add this please
and allow maintainers to edit your code
Author
|
check |
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.
If you are adding a new RPC, please answer the following questions.
Link the service provider's website (the company/protocol/individual providing the RPC):
https://www.vcrchain.com
Provide a link to your privacy policy:
If the RPC has none of the above and you still think it should be added, please explain why:
This PR registers a brand-new chain (VCR Chain, chainId 314169), not a
third-party RPC added to an existing chain. The endpoint
https://rpc.vcrchain.com is the chain's own canonical public node, operated
by the same team that runs the network — there is no external RPC provider
or commercial data processor involved, so a separate provider privacy policy
does not apply.
The node is a stock Hyperledger Besu client (besu/v26.7.0) serving standard
JSON-RPC. It is the only RPC in the array, so ordering does not apply.
Your RPC should always be added at the end of the array.