Cluster mempool is a proposal to associate each unconfirmed transaction in a mempool with related transactions, creating a cluster. Each cluster of transactions, whether it be a single transaction or several transactions, can be ordered from most desirable to mine to least desirable, allowing operations for adding or removing new clusters to complete fast enough to use them in P2P network code.

If P2P network code can determine whether a new unconfirmed transaction (or cluster of transactions) will improve the profitability of the mempool for miners in the near term, that criteria can be used instead of other heuristics for determining when a transaction package or replacement should be accepted. It is hoped that this will allow transaction relay to provide more flexible policy without exposing relay nodes to new resource-wasting attacks.

Primary code and documentation

Optech newsletter and website mentions


See also

Previous Topic:
Client-side validation
Next Topic:

Edit page
Report Issue