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

[Tracking] EngineAPI older versions #1187

Open
6 tasks done
Arkenan opened this issue Nov 15, 2024 · 1 comment
Open
6 tasks done

[Tracking] EngineAPI older versions #1187

Arkenan opened this issue Nov 15, 2024 · 1 comment
Assignees
Labels
engine-api Communication between Consensus and Execution

Comments

@Arkenan
Copy link
Collaborator

Arkenan commented Nov 15, 2024

We implemented the latest versions for newPayload, getPayload and forkchoiceUpdated. We should also implement the older versions so that we can benefit from engine-api hive tests that are meant for Paris and Shanghai versions but test most of our functionality.

We should implement all endpoints for each fork before going to the next one, so that we can unlock all hive tests for that version.

Paris (The merge)

Specs. This is the fork that most hive tests use.

Shanghai

Specs

@rodrigo-o
Copy link
Collaborator

Just for the record, this is the current state of the hive test related to the engine api before starting this task:

image

@rodrigo-o rodrigo-o self-assigned this Nov 18, 2024
@rodrigo-o rodrigo-o moved this to In Progress in ethrex_l1 Nov 18, 2024
@ElFantasma ElFantasma added the engine-api Communication between Consensus and Execution label Dec 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
engine-api Communication between Consensus and Execution
Projects
Status: In Progress
Development

No branches or pull requests

3 participants