params: reject chain config missing blobSchedule when Osaka is enabled - #1021
Open
ian0371 wants to merge 1 commit into
Open
params: reject chain config missing blobSchedule when Osaka is enabled#1021ian0371 wants to merge 1 commit into
ian0371 wants to merge 1 commit into
Conversation
A hand-written genesis that enables Osaka without a blobSchedule nil-dereferenced in ChainConfig.BlobConfig, killing an EN on a single eth_feeHistory call and panicking a CN at block-1 validation. CheckConfigForkOrder now requires a valid Osaka blob schedule (with non-zero baseFeeUpdateFraction, which is a division denominator) so such a config is rejected at load, and BlobConfig is nil-safe as a second layer.
hyunsooda
approved these changes
Aug 7, 2026
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.
A hand-written genesis that enables Osaka without a blobSchedule nil-dereferenced in ChainConfig.BlobConfig, killing an EN on a single eth_feeHistory call and panicking a CN at block-1 validation.
CheckConfigForkOrder now requires a valid Osaka blob schedule (with non-zero baseFeeUpdateFraction, which is a division denominator) so such a config is rejected at load, and BlobConfig is nil-safe as a second layer.
Types of changes
Checklist
I have read the CLA Document and I hereby sign the CLAin first time contribute after having read CLA$ make test)Related issues
Further comments