mempool: reject TXs that exceed consensus covenant block limits #768
Conversation
This file contains 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
pinheadmz
force-pushed
the
policy-limits
branch
from
e50090d
to
5e9be79
Compare
nodech
approved these changes
Dec 22, 2022
nodech
added
mempool
pinheadmz
force-pushed
the
policy-limits
branch
from
5e9be79
to
2f027e9
Compare
pinheadmz
added a commit
that referenced
this pull request
Dec 22, 2022
nodech
added
breaking-minor
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Users have been able to broadcast huge batches with 1,000 OPENs in a single TX. That would make an entire block invalid, so there's no reason to relay such a TX. We could also decide to add a POLICY rule that restricts this even further (the recent wallet batching work limits to like 200)