feat(proxy): Forward requests via JSON RPC endpoint #1
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
0xKitsune
changed the title
0xOsiris
approved these changes
Feb 7, 2025
|
Let's patch tests, and lints |
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.
Currently,
rollup-boostforwards all requests other than Engine API requests via the auth RPC endpoint. This requires that client implementations expose all methods inFORWARD_REQUESTSthrough their auth RPC endpoint, however this is not the case forop-geth. This PR introduces the--l2-http-urland--builder-http-urlflags to forward all requests via the JSON RPC api (other than Engine API requests).