Update EIP-7892: clarify one-time enabling change and config-only BPO forks #10812
+10
−4
Conversation
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
2 participants
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.
This change resolves a contradiction in EIP-7892 where the text claimed that BPO forks require no client-side code changes while also modifying EIP-4844 functions. The specification now explicitly introduces a one-time enabling change in both execution and consensus clients to source blob parameters from per-fork schedules (EL via EIP-7840’s blobSchedule and CL via BLOB_SCHEDULE). After these enabling changes are implemented, subsequent BPO forks become configuration-only and do not require additional client code changes. The definition section is updated to reflect this, an “Enabling change” subsection is added to make the scope unambiguous, the execution layer activation language is corrected to reference activation timestamps rather than slot numbers and the EL/CL alignment requirement now ties EL timestamps to the CL epoch start time. The requires header is updated to include 4844 because the proposal normatively parameterizes the EIP-4844 blob fee computation on the active schedule.