Update EIP-7928 define engine api methods #727
+205
−45
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Moving the BAL outside of the EL block (see here) meant we needed a separate method to retrieve BALs at the cl.
This PR implements engine_getBlockAccessListsByHashV1 and engine_getBlockAccessListsByRangeV1 methods to retrieve RLP-encoded block access lists as defined in EIP-7928. These methods enable consensus layer clients to obtain historical block access lists for synchronization with re-execution, with retention required for at least the weak subjectivity period (3533 epochs).
EIP changes for context:
https://github.com/ethereum/EIPs/pull/10940/files