Add payload_status field to AttestationData
#4655
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR proposes a structural clarification to the
AttestationDatacontainer by renaming theindexfield topayload_status. This field has been unused for its original purpose (committee index designation) since the Electra upgrade and is now repurposed to explicitly signal the status of the execution payload of the attested-to block. The underlyinguint64type is retained to ensure structural stability and provide extensibility for future payload statuses.The continued existence of
the attestation_data.indexfield in its legacy form presents several issues:Risk: Any modification to AttestationData can have wide-ranging and subtle effects.
Mitigation: This change is strictly a rename and does not alter the size, SSZ structure, or serialisation of the container. By avoiding a type change (e.g., to an enum), we minimise the scope of downstream code changes and reduce the risk of introducing new bugs.
Related Links
Context: EIP-7732 Breakout Call #25
Discussion: Discord Thread on Ethereum R&D