fix(devnet): Modify the blob configuration of the bsc devnet #212
Conversation
This file contains 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.
Description
In the deployment script of the BSC devnet, there are two configurations
DefaultExtraReserveForBlobRequestsandMinBlocksForBlobRequests, which determine how many block heights of blob data L1 retains. The default values of 32 and 576 are too short for L2, which causes issues when testing opBNB devnet locally.Rationale
Update the deployment script to increase the default values of
DefaultExtraReserveForBlobRequestsandMinBlocksForBlobRequeststo 524288, which is the default value in production.Example
none
Changes
Notable changes:
DefaultExtraReserveForBlobRequestsandMinBlocksForBlobRequeststo 524288