fix: exclude L1 message from block payload size validation #476
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.
1. Purpose or design rationale of this PR
Currently, both
worker
andblock_validator
consider L1 messages when enforcing the block payload size limit. This is wrong (an unnecessary over-estimation), since L1 messages are not part of the batch payload.It is risky to merge this fix in this form. It has the risk that we produce a block that's valid according to the updated size limit, but is still rejected by old-version nodes. This risk is limited by the fact that we currently only allow 10 L1 messages per block. An alternative, safer roll-out is:
block_validator
part.worker
part.2. PR title
Your PR title must follow conventional commits (as we are doing squash merge for each PR), so it must start with one of the following types:
3. Deployment tag versioning
Has the version in
params/version.go
been updated?4. Breaking change label
Does this PR have the
breaking-change
label?