Update EIP-7892: harden BPO forks spec.#9818
Closed
raulk wants to merge 5 commits intoethereum:masterfrom
Closed
Conversation
github-actions
bot
added
c-update
Collaborator
File
|
raulk
changed the title
tersec
reviewed
May 25, 2025
Member
Author
|
Following further discussion on Discord, I posted a synthesis of current consensus/opinions and recommendation here: ethereum/consensus-specs#4331 (comment) |
rolfyone
reviewed
May 28, 2025
EIPS/eip-7892.md
Outdated
| ``` | ||
| BLOB_SCHEDULE: | ||
| - EPOCH: 348618 | ||
| A new `BLOB_PARAMETER_SCHEDULE` field is added to consensus layer configuration, containing a sequence of entries representing blob parameter changes after `ELECTRA_FORK_EPOCH`. This replaces the deprecated `MAX_BLOB_PER_BLOCK{_FORKNAME}` convention for future forks, while preserving existing entries for previous forks. |
There was a problem hiding this comment.
why are we renaming the blob schedule? we can just do this under blob_schedule still unless we're worried about old parsers breaking or something... The blob_schedule already resulted in objects and we're just adding an attribute imo..
Member
Author
There was a problem hiding this comment.
This is a leftover from a previous version that backported Deneb and Electra. Fixing.
jtraglia
reviewed
May 28, 2025
jtraglia
reviewed
May 28, 2025
jtraglia
reviewed
May 28, 2025
jtraglia
reviewed
May 28, 2025
rolfyone
reviewed
May 30, 2025
Member
Author
|
Superseded by #9840. |
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
5 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 is a minimal changeset on top of the existing BPO hardforks spec to solve some loose ends.
Concretely, this adjusts the following at the consensus layer:
fork_versionto pure BPO forks.compute_fork_version()to take BPO forks into account.Furthermore, this makes a broader adjustment to avoid future ambiguity:
While thinking through this, I realized there may be value in formalizing the broader concept of "parametric forks" by defining how they interact with regular hard forks, establishing a process for bringing additional parameters under this management mechanism, and iterating on client config schemas (https://github.com/eth-clients) to introduce time-based triggers as a top-level organizational axis. Perhaps the subject of a future proposal.