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 Peter Todd

Posted on: July 22, 2024 11:45 UTC

The discourse revolves around the technical aspects of Bitcoin transactions, specifically addressing the challenges and solutions related to transaction pinning in the context of the Lightning Network and proposed upgrades to Bitcoin Core's Replace-By-Fee (RBF) policy.

Transaction pinning poses a significant challenge in protocols like Lightning, where an adversary could potentially broadcast a large, low-fee transaction to prevent a counterparty's transaction from being confirmed due to package size limits. The introduction of Child Pays For Parent (CPFP) carve-outs was a measure designed to mitigate this issue by allowing a transaction with one unconfirmed parent to slightly exceed these limits, facilitating the confirmation of essential transactions in such scenarios.

However, the conversation introduces the concept of cluster Replace-By-Fee for Replacements (RBFR), which is posited as making CPFP carve-outs obsolete by addressing the root cause of pinning more directly through package replacement. Package replacement allows for the evaluation of transactions and their parents as a single package, enabling users to outbid a low-fee transaction that attempts to pin another transaction by offering a higher fee for the whole package. This approach simplifies the resolution of pinning issues by considering the fee rate of the entire transaction package rather than individual transactions.

Furthermore, the discussion critiques the Transaction Relay for Universal Consensus (TRUC) combined with a cluster mempool solution as not being a drop-in solution and necessitating a network-wide upgrade before it can be effective. In contrast, RBFR offers a more immediate solution to transaction pinning without requiring significant changes from users or waiting for network upgrades. RBFR not only addresses existing pinning problems in the Lightning Network but also presents a general fix for pinning issues across various use cases, highlighting its potential as a superior upgrade path compared to TRUC and cluster mempool proposals.

For further details on CPFP carve-outs and ongoing discussions, references are provided, including links to Bitcoin Operations and a Google Groups discussion. Peter Todd’s insights underscore the importance of adopting practical and efficient solutions to enhance the robustness and functionality of Bitcoin’s transaction handling mechanisms, particularly in supporting innovations like the Lightning Network.