RPC Overrides #1057
Merged
RPC Overrides #1057
Conversation
This file contains 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
rin-st
reviewed
Feb 24, 2025
technophile-04
approved these changes
Feb 25, 2025
technophile-04
approved these changes
Feb 25, 2025
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.
Problem
Currently, changing the RPCs for the frontend is a bit tricky since SE-2 assumes that you are going to use Alchemy, and tweaking it requires you to tweak
wagmiConfigand it's not very extract forward (we area bit vendor-locked with Alchemy)Solution
Let the builders define the
rpcOverridesinscaffold.config.ts. We don't want to pollute the config file, but RPC config seems like a top-level kind of config.Tried to come up with the simplest way that respect the current functionality.
Really open!!