# Cluster Mempool RBF Thoughts

**URL:** <https://delvingbitcoin.org/t/cluster-mempool-rbf-thoughts/156>\
**Category:** Implementation\
**Tags:** wg-cluster-mempool\
**Created:** [November 1, 2023, 2:06am UTC](https://delvingbitcoin.org/t/cluster-mempool-rbf-thoughts/156 "2023-11-01T02:06:07Z")\
**Posts on this page:** 1\
**Showing post:** 12

<div class="post-metadata">

**Author:** ![ajtowns](https://delvingbitcoin.org/user_avatar/delvingbitcoin.org/ajtowns/32/417_2.png) [@ajtowns](https://delvingbitcoin.org/u/ajtowns)\
**Post date:** [December 5, 2023, 4:06pm UTC](https://delvingbitcoin.org/t/cluster-mempool-rbf-thoughts/156/12 "2023-12-05T16:06:40Z")

</div>

The O(n^2) step to re-optimise the new chunks has to be performed per cluster (ie, it’s O(bc^2) where b is number of clusters, and c is chunks per cluster), so limiting the number of clusters that can be conflicted with would make sense. Affecting many clusters without actually combining those clusters as a result of the RBF seems like it would be unusual behaviour, too?

---

_[View the full topic](https://delvingbitcoin.org/t/cluster-mempool-rbf-thoughts/156)._