Skip to content

Cluster size 2 package rbf

Allows any 2 transaction package with no in-mempool ancestors to do package RBF when directly conflicting with other mempool clusters of size two or less.

Proposed validation steps:

  1. If the transaction package is of size 1, legacy rbf rules apply.
  2. Otherwise the transaction package consists of a (parent, child) pair with no other in-mempool ancestors (or descendants, obviously), so it is also going to create a cluster of size 2. If larger, fail.
  3. The package rbf may not evict more than 100 transactions from the mempool(bip125 rule 5)
  4. The package is a single chunk
  5. Every directly conflicted mempool transaction is connected to at most 1 other in-mempool transaction (ie the cluster size of the conflict is at most 2).
  6. Diagram check: We ensure that the replacement is strictly superior, improving the mempool
  7. The total fee of the package, minus the total fee of what is being evicted, is at least the minrelayfee * size of the package (equivalent to bip125 rule 3 and 4)

Post-cluster mempool this will likely be expanded to general package rbf, but this is what we can safely support today.

Merge request reports

Loading