fix: limit max block size#9757
Merged
Merged
Conversation
Collaborator
|
Probably why I saw a CPU spike on a dead network, right? |
ludamad
approved these changes
Nov 5, 2024
Collaborator
Author
|
I think so |
Maddiaa0
approved these changes
Nov 5, 2024
Maddiaa0
pushed a commit
that referenced
this pull request
Nov 6, 2024
I had seen a sequencer trying to build a block with 100+ transactions, which results in a death spiral. Also increase the timeout on discv5 for when that is supported across multiple nodes.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
I had seen a sequencer trying to build a block with 100+ transactions, which results in a death spiral.
Also increase the timeout on discv5 for when that is supported across multiple nodes.