feat(rollup): Engine RPC API #98
Draft
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
merklefruit
force-pushed
the
nico/feat/engine-api
branch
from
d645f86
to
89acec2
Compare
merklefruit
added
C-enhancement
mattsse
reviewed
Sep 23, 2024
There was a problem hiding this comment.
fyi, with alloy-rs/alloy#1314 you likely dont need the additional transport stuff I assume
cool, hadn't seen this, ty |
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.
Overview
This PR adds an Engine RPC API client using the new
op_alloy_provider::ext::engine::OpEngineApi.It also adds an authenticated transport borrowed from Reth's.
Note
This is not compiling right now, because of inconsistencies between the op_alloy version used by Kona and Op-rs.
We can move forward by patching Kona if needed for testing.
Meta