Splitting more block, addr and tx classes of network traffic

Antoine's email outlines progress in developing a native multi-process architecture aimed at enhancing traffic class isolation by utilizing different runtimes, while still sharing the "old" block store across these isolated runtimes. This architectural approach addresses some of the explicit signaling concerns previously discussed, acknowledging their validity and the privacy issues raised with the proposal of adding a signaling bit for full-replace-by-fee (RBF) peers. The conversation around this topic is reflective of ongoing discussions within the community on how best to balance functionality and privacy.

The design’s primary challenge lies in its potential to increase the number of inbound sockets required per peer, particularly noticeable in scenarios involving a "cold block" archive process where the connection is initiated by the inbound peer. Despite this, the implementation of messages following the Bitcoin Improvement Proposal (BIP) 0338 standard is viewed as advantageous, especially in terms of outbound bandwidth consumption for full-node peers that adopt it. This improvement is not only beneficial for these nodes but also supports more efficient ingress filtering at the network level, indicating a thoughtful consideration of broader network health and efficiency.

This technical discourse highlights an active exploration of solutions to improve Bitcoin's underlying systems, focusing on the trade-offs between scalability, privacy, and operational efficiency. Such discussions are crucial for the evolution of Bitcoin's infrastructure, ensuring it remains robust, secure, and adaptable to the growing demands of its user base.