feat: make Reth RPC APIs configurable - #43
Open
kejan2514 wants to merge 3 commits into
Open
Conversation
|
nice job |
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
Make the Reth HTTP and WebSocket RPC API namespaces configurable through environment variables while keeping safer defaults.
Changes
RETH_HTTP_APIandRETH_WS_APIconfiguration.eth,net,web3.--http.apiand--ws.api.debug,txpool, orminer.Motivation
RPC namespaces should be configurable by node operators instead of exposing a broader fixed set by default.
This provides safer defaults while preserving flexibility for deployments that require additional APIs.
Closes #42