Update EIP-7377: clarify storage tuple processing in EIP-7377 #10982
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.
Fix
Clarifies ambiguous wording in the storage tuple processing specification that could be misinterpreted.
Changes
tx.storageand the sender's storage trie" with explicit "for each tuple(slot, value)intx.storage"t.first/t.secondnotation in favor of descriptive tuple structure(slot, value)tx.storageare processed, not the existing storage trie