bitcoin-dev

A "Free" Relay Attack Taking Advantage of The Lack of Full-RBF In Core

A "Free" Relay Attack Taking Advantage of The Lack of Full-RBF In Core

Original Postby Antoine Riard

Posted on: July 19, 2024 13:52 UTC

The email from Antoine to Peter Todd addresses a specific scenario involving Bitcoin transactions and potential vulnerabilities in the network's handling of transaction broadcasts and double-spending.

Antoine describes a situation where Alice attempts to exploit the Bitcoin network by broadcasting two versions of a transaction. Initially, Alice sends a low-fee transaction (A) to the majority of miners and network nodes, which does not opt into replace-by-fee (RBF), followed by a high-fee double-spend transaction (A2) to a single miner named Mark. Due to the network's design, nodes do not relay transaction A to Mark and vice versa, preventing Mark from relaying A2 back to the network nodes.

Further complicating the issue, Alice broadcasts a child transaction (B) of the original transaction (A) to the majority of the network, attempting to leverage the network's bandwidth further. Mark eventually confirms the double-spend transaction A2 in a block, effectively rendering the efforts and resources spent on transactions A and B as wasted bandwidth. Antoine points out that the efficiency of this attack, in terms of bandwidth wastage, depends on how quickly transaction A2 is included in Mark's block template and mined. The implication is that the higher Mark's hash rate resources, the less latency there would be for transaction B to propagate across the network or for Alice to rebroadcast it cyclically.

Antoine concludes with an open question regarding the time elapsed between the private reporting of this issue to a security mailing list and the public disclosure of Peter Todd's email, suggesting concern over the handling and communication of vulnerabilities within the community. This highlights the broader context of security practices and responsible disclosure in the blockchain ecosystem.