Update rpc structure#664
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
engn33r
approved these changes
Apr 19, 2026
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
2 participants
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
PublicClientinstances based on frontmatterrpcCalls[].chainVITE_RPC_URI_FOR_<chainId>pattern with Yearn RPC defaultsscripts/fetchedAddressData.jsonand the twonatspec/lib/*submodule pointer updates)Why
The docs repo previously hardcoded mainnet Alchemy in both runtime and address-check paths even though docs frontmatter already carries chain metadata. This change makes the RPC layer match the chain-based setup used in
yearn.fiand leaves mainnet-only behavior only where that is still actually true today.