An overview of the cluster mempool proposal

Posted by instagibbs

Feb 2, 2024/15:36 UTC

In the realm of transaction management within networked systems, there are inherent challenges associated with accommodating new transactions by displacing existing ones. The concept of relying on peers to identify which transactions to evict is flawed because it's not always feasible for a peer to be aware of all other transactions in the network. This approach also has limited applicability as it is only suitable for certain network topologies.

Moreover, the premise that wallets can efficiently make eviction decisions themselves is questionable. Such a mechanism would need to be well justified and thought out, especially when considering the long-term vision of package relay networks. In the current landscape, where one-input-one-coin (1p1c) scenarios are prevalent, the necessity for sophisticated eviction strategies seems less pressing.

Looking towards the future, the conversation shifts towards "top block" methodologies, which could reshape the transaction selection process. In this context, sibling eviction, which is currently deemed of secondary importance, may gain relevance. A potential strategy for sibling eviction could involve simplifying the process to only exclude transactions that are not ancestors or descendants from consideration, thereby streamlining the eviction process in these evolved network structures.

Link to Raw Post
Bitcoin Logo

TLDR

Join Our Newsletter

We’ll email you summaries of the latest discussions from authoritative bitcoin sources, like bitcoin-dev, lightning-dev, and Delving Bitcoin.

Explore all Products

ChatBTC imageBitcoin searchBitcoin TranscriptsSaving SatoshiBitcoin Transcripts Review
Built with 🧡 by the Bitcoin Dev Project
View our public visitor count

We'd love to hear your feedback on this project?

Give Feedback