Skip to content

Conversation

@rach-id
Copy link
Member

@rach-id rach-id commented Dec 1, 2025

Closes #2694

@rach-id rach-id self-assigned this Dec 1, 2025
@rach-id rach-id requested a review from evan-forbes as a code owner December 1, 2025 11:55
propagator = propagationReactor

if config.Consensus.EnableLegacyBlockProp {
types.MaxBlockSizeBytes = types.ReducedMaxBlockSizeBytes // reduce the max block size to avoid overloading the legacy block prop mechanism
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is this consensus breaking? like, do we use the var to validate blocks or only for our own usage

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this is used when receiving the proposal and block parts. So if we run a binary with a max block size bytes of 8mb, whenever anyone sends an >8mb block, we won't accept its proposal or block parts.
also when proposing, we will only propose blocks that are < 8mb.

So if we enable and the network is producing 128mb blocks, we won't be able to follow it.

We want this in case the propagation reactor fails, we can switch to this and make sure the network stays alive with reduced throughput

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Reduce the block size also when only the legacy block prop is running

3 participants