Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat(rollup): Engine RPC API #98

Closed
wants to merge 1 commit into from
Closed

Conversation

merklefruit
Copy link
Collaborator

@merklefruit merklefruit commented Sep 22, 2024

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

@merklefruit merklefruit self-assigned this Sep 22, 2024
@merklefruit merklefruit added C-enhancement New feature or request A-rollup Area: rollup crate labels Sep 22, 2024
@merklefruit
Copy link
Collaborator Author

@refcell should this live under the rpc crate started in #35?

Copy link
Member

@mattsse mattsse left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

fyi, with alloy-rs/alloy#1314 you likely dont need the additional transport stuff I assume

@merklefruit
Copy link
Collaborator Author

fyi, with alloy-rs/alloy#1314 you likely dont need the additional transport stuff I assume

cool, hadn't seen this, ty

refcell added a commit that referenced this pull request Oct 18, 2024
This PR supercedes and replaces #98 

### Overview

* re-implemented engine functionality, using the latest Alloy jwt-auth
layer + OpEngineApi extension trait
* removed `AttributesValidator` trait because I don't think it will be
useful since we need to work with the engine API anyway for other
reasons, other than validating payloads: namely updating the fork choice
and driving the EL forward.

I believe the decision to remove the validator trait will pay off in the
future because it allows us to work with the engine api more freely.
However if it turns out to be a bad decision this can be reverted easily
as well.

---------

Co-authored-by: refcell <abigger87@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-rollup Area: rollup crate C-enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

feat(rpc): Engine API
2 participants