Skip to content

fix: bpo spec initialization for genesis#7779

Closed
barnabasbusa wants to merge 2 commits intostatus-im:stablefrom
barnabasbusa:bbusa/fix-bpo-spec
Closed

fix: bpo spec initialization for genesis#7779
barnabasbusa wants to merge 2 commits intostatus-im:stablefrom
barnabasbusa:bbusa/fix-bpo-spec

Conversation

@barnabasbusa
Copy link

The code was checking if currentBPO.EPOCH.uint64 != 0.uint64 before 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:

    "BLOB_SCHEDULE": [
      {
        "EPOCH": "0",
        "MAX_BLOBS_PER_BLOCK": "15"
      }
    ],

@github-actions
Copy link

github-actions bot commented Dec 5, 2025

Pull requests to the stable branch are not allowed.
Please open your pull request against the unstable branch.
See https://nimbus.guide/contribute.html#build-and-deploy

@github-actions github-actions bot closed this Dec 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant