feat(tests): add invalid BAL tests for spurious block_access_index #1953
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.
ποΈ Description
This PR adds three negative test cases that ensure clients reject blocks whose Block Access List contains an out-of-range
block_access_index(len(transactions)+2). The suite covers (1) a spurious storage entry whose slot is also legitimately read by another transaction, (2) the same but with a legitimate write, and (3) no other transactions touching the slot. In all variants, the block must be rejected withINVALID_BLOCK_ACCESS_LIST, ensuring strict bounds-checking of BAL indices independent of whether the referenced(address, slot)is otherwise accessed in-block.π Related Issues or PRs
EIP clarification ethereum/EIPs#10990
β Checklist
toxchecks to avoid unnecessary CI fails, see also Code Standards and Enabling Pre-commit Checks:uvx tox -e statictype(scope):.mkdocs servelocally and verified the auto-generated docs for new tests in the Test Case Reference are correctly formatted.@ported_frommarker.Cute Animal Picture