Repository navigation
Enable privacy services when an Ethereum RPC is configured - #54
Merged
Merged
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
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.
When an operator configures an Ethereum mainnet privacy RPC, the pool index and relayer directory remain disabled unless two additional flags are set. Enable each service by default when that RPC is configured, while retaining independent
falseopt-outs and failing explicitly enabled services with no RPC.An installation without an RPC still starts with both services disabled. A newly configured endpoint remains idle until its first request; previously activated pools and directory checkpoints retain their restart behavior. No provider is selected automatically. Documentation now calls out RPC quota, possible provider charges, public endpoint activation and privacy logging.
Validation: 141 focused tests across five suites passed on Node 26. The full Jest suite passed 1,642 tests before one additional configuration test was added; the final-head full suite is running in CI. No live services or data were changed.