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

feature: Add engine API execution payload information in fixtures #183

Merged
merged 8 commits into from
Jul 5, 2023

Conversation

marioevz
Copy link
Member

Allows tests to specify the metadata that describes how each block in a blockchain test should be delivered through the Engine API, which is used in hive testing.

The forks now also have information about the versions of the Engine API endpoints that should be used with all the payloads generated for them.

Currently only engine_newPayloadVX is supported.

@marioevz marioevz requested a review from spencer-tb July 3, 2023 18:29
Copy link
Collaborator

@spencer-tb spencer-tb left a comment

Choose a reason for hiding this comment

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

Thanks for adding this! I was able to remove so many lines in the pyspec simulator as a result 💯

I think we could add a flag for this in the future. If at some point by default we generate the original StateTest format when running fill in the future we could add the --hive or --pyspec flag for generating these fixtures with the payloads

src/ethereum_test_tools/common/types.py Outdated Show resolved Hide resolved
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants