Mempool cluster limits#2063
Draft
ImplOfAnImpl wants to merge 6 commits into
Draft
Conversation
…tes to RunOptions; fix test wallet_high_fee.py
…the size of a single tx. Update the changelog.
This was referenced May 22, 2026
f4ff234 to
9661f7f
Compare
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
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.
Mempool will now reject a tx if adding it would form a cluster with tx count or byte size above the limits.
I also exposed MempoolConfig in the node RPC. At the moment, the wallet only uses it to limit the single tx size in places where
chain_config.max_tx_size_for_mempool()was previously used. Note that this single tx size limiting isn't (and wasn't) particularly accurate, but fixing it here doesn't make much sense. IMO the wallet's whole utxo selection mechanism has to be revamped, I added the corresponding TODOs.