Refactor #isPrecompiledAccount to support non-consecutive accounts #2829
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.
The
#isPrecompiledAccountcheck currently uses an upper bound approach, validating addresses in the range[1, UB]. This worked because all precompiled contracts were at consecutive addresses (1-17 for Prague).EIP-7951 introduces P256VERIFY at address 0x100 (256), breaking the contiguous assumption.
This PR removes the
#precompiledAccountsUBand constructs the set of addresses for each schedule instead.#isPrecompiledAccounts(ACCTCODE, SCHEDULE)is updated to check ifACCTCODEis in#precompiledAccountsSet(SCHEDULE).