Repository navigation
feat(specs,tests): record the EIP-8250 activation in the fork block's access list - #3722
Open
spencer-tb wants to merge 3 commits into
Open
spencer-tb wants to merge 3 commits into
spencer-tb wants to merge 3 commits into
Conversation
2 tasks done
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## eips/bogota/eip-8250 #3722 +/- ##
=======================================================
Coverage ? 94.94%
=======================================================
Files ? 677
Lines ? 41926
Branches ? 3962
=======================================================
Hits ? 39805
Misses ? 1467
Partials ? 654
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
2 tasks done
spencer-tb
added
A-spec-specs
spencer-tb
marked this pull request as ready for review
October 6, 2026 12:54
…n schedule Co-authored-by: Jochem Brouwer <29359032+jochem-brouwer@users.noreply.github.com>
…ock's access list
…l in the fork block
spencer-tb
force-pushed
the
eip-8250-bal-activation
branch
from
October 6, 2026 17:01
ac4b6ae to
3d6b174
Compare
This was referenced Oct 6, 2026
gurukamath
added a commit
to gurukamath/execution-specs
that referenced
this pull request
Oct 7, 2026
Review follow-up for ethereum#3729. EIP-8250 installs its nonce manager through `activation_code_installs` on `eips/bogota/eip-8250`, and ethereum#3722 and ethereum#3725 build on it, so removing the hook here would break that install when the branches merge. Restore the hook, Frontier's empty implementation, both blockchain filler call sites, the Hive genesis builder, the pre-allocation group builder, and `Alloc.with_installed_code`, all as they are on the base branch. Only the EIP-8141 override stays removed: the expiry verifier is a predeploy, not an activation install. The `with_installed_code` docstring no longer names an EIP as its example. Reword the `EXPIRY_VERIFIER` docstring and the fork transition test module docstring as suggested in review.
This branch has not been deployed
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
1 participant
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
Merge order: after #3557 and ethereum/EIPs#12406. #3725 is stacked on this.
Records the EIP-8250 nonce manager install at block access index 0 of the fork block, as proposed in ethereum/EIPs#12406 and as Nethermind, reth and ethrex already do.
The spec now applies the install in the fork block itself instead of in
apply_fork, detected byis_fork_blockas EIP-8253 does in #3535. The t8n derives the fork block from the transition schedule through #3557, so there is no separate activation flag, and the filler no longer pre-installs the nonce manager.Related Issues or PRs
Checklist
just static<type>(<area>): <title>, where<type>and<area>come from an appropriateC-<type>, respectivelyA-<area>, label. The title should match the target squash commit message.