Update EIP-7928: Update StorageKey and StorageValue type definitions#10817
Merged
eth-bot merged 1 commit intoethereum:masterfrom Nov 26, 2025
Merged
Conversation
github-actions
bot
added
c-update
Collaborator
|
✅ All reviewers have approved. |
nerolation
approved these changes
Nov 26, 2025
Contributor
nerolation
left a comment
nerolation
left a comment
There was a problem hiding this comment.
lgtm.
Related to discussion here:
https://discord.com/channels/595666850260713488/1364000387195076608/1441256320459214949
eth-bot
approved these changes
Nov 26, 2025
Collaborator
eth-bot
left a comment
eth-bot
left a comment
There was a problem hiding this comment.
All Reviewers Have Approved; Performing Automatic Merge...
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
3 participants
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 updates the StorageKey and StorageValue block access list type definitions to uint256.
The reasoning for this change is to reduce the size of the rlp encoded BALs. The rlp encoding of small slots takes less space when encoded as a number than when encoded as bytes32. For example the uint256 rlp encoding of slot 1 takes a single byte while the bytes32 rlp encoding takes 33 bytes due to the leading zeros which can/should be excluded to save space.