Skip to content

txpool: activate the new max blobs per transaction post Osaka#32562

Closed
MqllR wants to merge 1 commit into
ethereum:masterfrom
MqllR:maxblobs_tx
Closed

txpool: activate the new max blobs per transaction post Osaka#32562
MqllR wants to merge 1 commit into
ethereum:masterfrom
MqllR:maxblobs_tx

Conversation

@MqllR
Copy link
Copy Markdown
Contributor

@MqllR MqllR commented Sep 9, 2025

#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

@MqllR MqllR requested a review from rjl493456442 as a code owner September 9, 2025 10:26
@MqllR MqllR changed the title fix: activate the new max blobs per transaction post Osaka txpool: activate the new max blobs per transaction post Osaka Sep 9, 2025
@rjl493456442
Copy link
Copy Markdown
Member

We have this soft blob limitation in the Geth, which is 6. This rule is applied regardless Osaka fork is activated or not.

@MqllR
Copy link
Copy Markdown
Contributor Author

MqllR commented Sep 9, 2025

@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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Osaka's Max blobs per transactions new value is applied to before proper hardfork

2 participants