🗒️ Description

• Increase BAL coverage. Some expectations and tests in first commit here were based on the claims from this repository: https://github.com/catwith1hat/evm-breaker, though investigation led to most of the reported cases already being covered in the tests here and clients seem to be passing these. Either way, BAL expectations were added to some tests that cover similar scenarios as guardrails, and some novel test scenarios came out of this as well and were added here. Test cases that seem genuinely novel from evm-breaker audit that were added in this PR (5/18):
  • #167: test_bal_7702_invalid_authority_has_code_authorization — auth fails because authority has pre-existing non-delegation code; authority loaded then rejected, must appear in BAL with empty change
    set.
  • #180: test_bal_7702_multi_hop_delegation_chain — A→B→C delegation chain; CALL(A) resolves one hop only, third address must not appear in BAL.
  • #165: test_bal_create_storage_op_then_selfdestruct_same_tx — same-tx CREATE/CREATE2 + SLOAD/SSTORE on slot B + SELFDESTRUCT; slot B must appear in storage_reads, never storage_changes, and
    destroyed contract has no nonce/code changes.
  • #165: test_bal_create2_selfdestruct_then_recreate_same_block — Tx1 CREATE2+SELFDESTRUCT then Tx2 CREATE2 at same address; Tx1 entry has no nonce/code changes, Tx2 entry has fresh nonce+code at the
    same address.
  • #165: test_selfdestruct_send_to_sender — pre-existing contract SELFDESTRUCTs to tx.sender; sender's BAL entry coalesces nonce_changes (as sender) and balance_changes (as beneficiary).
• Since I was already here I did a quick scan for some related tests of interest against what exists and added a few more cases here in a second commit to increase the coverage even more.
• The third commit here closes out missing test cases reported in EIP-7928 BAL: missing test coverage for direct DELEGATECALL/CALLCODE to a precompile (bal-devnet-7) #2830 from Nethermind precompile-specific paths.

Bonus: I changed all the fork.header_bal_hash_required() checks in tests that append a BAL expectation to fork.is_eip_enabled(7928), now that this API is available, as I think it is more readable / desirable this way.

✅ Checklist

• All: Ran fast static checks to avoid unnecessary CI fails, see also Code Standards and Enabling Pre-commit Checks:

  just static

• All: PR title adheres to the repo standard - it will be used as the squash commit message and should start type(scope):.
• All: Considered updating the online docs in the ./docs/ directory.
• All: Set appropriate labels for the changes (only maintainers can apply labels).
• Tests: Ran mkdocs serve locally and verified the auto-generated docs for new tests in the Test Case Reference are correctly formatted.
• Tests: For PRs implementing a missed test case, update the post-mortem document to add an entry the list.
• Ported Tests: All converted JSON/YML tests from ethereum/tests or tests/static have been assigned @ported_from marker.

Cute Animal Picture