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

support calling engine api #69

Open
ncitron opened this issue Oct 21, 2022 · 2 comments
Open

support calling engine api #69

ncitron opened this issue Oct 21, 2022 · 2 comments
Labels
feat New feature or request

Comments

@ncitron
Copy link
Collaborator

ncitron commented Oct 21, 2022

For integrating with EL full nodes, we should support calling the engine api, specifically engine_forkchoiceUpdatedV1, which Akula uses to follow the chain.

@ncitron ncitron added the feat New feature or request label Oct 21, 2022
@dadepo
Copy link
Contributor

dadepo commented Nov 8, 2022

Just to be clear, the purpose is to be able to drive the EL by making this call? What about the engine_newPayloadV1 call. Should that not also be included?

@ncitron
Copy link
Collaborator Author

ncitron commented Nov 8, 2022

Yep. Eventually we probably want to support all the parts of driving the execution layer, but engine_forkchoiceUpdatedV1 is a good one to start with because it turns out Akula only uses that one.

We also probably want to both drive the API directly, and to provide a separate interface (maybe using tokio channels), so that this could be built into Akula directly with no API intermediary needed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feat New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants