txpool: activate the new max blobs per transaction post Osaka #32562
Conversation
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
MqllR
changed the title
Member
|
We have this soft blob limitation in the Geth, which is 6. This rule is applied regardless Osaka fork is activated or not. |
Author
|
@rjl493456442 before geth 1.16.2, the max blobs limit was 7 not 6 see. This is a breaking change for our blob txs which blocks us to upgrade our nodes until we patch our L2. |
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.
#32246 changed the max blobs through a post Osaka condition in the state transition. But the txpool validation doesn't look at the fork and just apply the global max blobs new param breaking the pre-osaka parameters.
This PR closes #32560