Disclosure of DoS due to inv-to-send sets growing too large

Headline:
Disclosure of DoS due to inv-to-send sets growing too large

Summary:
This lead was identified from Bitcoin Core Blog. It has been saved for accountability coverage and should be reviewed against the original source before expansion.

What the record says:
The source headline is: Disclosure of DoS due to inv-to-send sets growing too large. The source summary says: Before Bitcoin Core v25.0, the per-peer m_tx_inventory_to_send sets could grow too large to a point where sorting these sets when constructing inventory messages would affect the node’s ability to communicate with its peers. Network conditions in early May 2023 triggered this DoS and affected block and transaction propagation. This issue is considered Medium severity. Details As part of transaction relay, Bitcoin Core maintains a per-peer m_tx_inventory_to_send set with transactions that should be announced to the peer. When constructing an inventory message for a peer, the set is sorted by transaction dependencies and feerate to prioritize high-feerate transactions and to avoid leaking the order the node learned about the transactions. Before Bitcoin Core v25.0, when constructing inventory messages, relevant (still in mempool, not yet announced to us by the peer, above the fee filter) t

Why it matters:
This may be relevant to public accountability, consumer protection, government oversight, fraud monitoring, or financial transparency depending on the source record.

What is not yet proven:
This draft should not be treated as proof beyond what the linked source directly supports. Avoid adding accusations, private information, or copied text from the original source.

Source:
https://bitcoincore.org/en/2024/10/08/disclose-large-inv-to-send/

AI writer note: OPENAI_API_KEY is empty, so this was generated with the built-in safe fallback writer.