Post-clustermempool package RBF: per-chunk processing

Post-clustermempool package RBF: per-chunk processing

Original Postby ajtowns

Posted on: November 15, 2023 03:05 UTC

In the discussion regarding transaction processing and mempool management within a blockchain network, the focus is on whether it is practical to pass on information about transactions that have been accepted into the mempool, especially in scenarios where certain transactions are prioritized due to higher fees or are dependent on other transactions.

A suggestion was made to potentially recognize transactions that pay Denial-of-Service (DoS) fees for higher priority or to keep track of transactions orphaned specifically for DoS reasons. This would allow for such transactions to be retried when their high-fee child transactions are announced.

However, there's an inclination towards initially omitting this feature, with the possibility of introducing it later as an improvement. The rationale behind this approach includes considerations of simplicity and the likelihood that the scenario may not occur frequently enough to justify immediate implementation. This decision aligns with the Keep It Simple, Stupid (KISS) principle, emphasizing the importance of maintaining straightforward and uncomplicated systems.

Despite reservations, there's acknowledgment of the potential usefulness of reliably implementing such a feature. It is recognized that accurately tracking and managing these interdependent transactions could enhance the efficiency and reliability of the network's transaction handling capabilities.