fix: bpo spec initialization for genesis#7779
Closed
barnabasbusa wants to merge 2 commits intostatus-im:stablefrom
Closed
fix: bpo spec initialization for genesis#7779barnabasbusa wants to merge 2 commits intostatus-im:stablefrom
barnabasbusa wants to merge 2 commits intostatus-im:stablefrom
Conversation
|
Pull requests to the |
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
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 code was checking if
currentBPO.EPOCH.uint64 != 0.uint64before adding blob schedule entries.This incorrectly filtered out epoch 0 (genesis), causing the API to return an empty BLOB_SCHEDULE array when BPO was scheduled for epoch 0. Probably the check was supposed to be for
MAX_BLOBS_PER_BLOCK?This PR results in nimbus returning for BPO_1 scheduled to epoch 0: