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

Remove latest_execution_payload_header from the beacon state #3612

Open
potuz opened this issue Feb 29, 2024 · 0 comments
Open

Remove latest_execution_payload_header from the beacon state #3612

potuz opened this issue Feb 29, 2024 · 0 comments
Labels
general:enhancement New feature or request

Comments

@potuz
Copy link
Contributor

potuz commented Feb 29, 2024

The Beacon State tracks the latest execution payload header in full, but the only thing that this is used for is to check that the parent hash is the right one. We should only track the latest block hash instead.

Every change in the execution header forces clients to keep these changes on the beacon state and track new structures. There have been numerous marshalling bugs because of endinannes, large number libraries need to be imported and maintained up to date on the CL without any need since these structures should be opaque as they are not used on the CL.

@hwwhww hwwhww added the general:enhancement New feature or request label Mar 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
general:enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants