Published on: 2022-10-10T22:05:38+00:00
The email conversation on the bitcoin-dev mailing list revolves around the issue of stuck transactions caused by the minimum fee rate policy and proposes a solution through package relay. The objective is to propagate incentive-compatible transactions for mining, even if they don't meet the minimum feerate alone.The discussion raises questions about the complexity of solutions, the potential impact of covenants, and the predictability of pre-signed transaction rejection by nodes. Matt Corallo's thoughts are also mentioned, emphasizing the need for parent transactions to be relayed along with their higher feerate children. The email further explores the implications of changing transaction order in a package and the potential for attack vectors such as front running or MEV. It concludes that any policy beyond what is published via the protocol will cause problems.The proposed Package Relay Proposal aims to optimize transaction packaging and prevent orphaned transactions. It suggests that each node should package transactions for its peers based on individual fee rates, eliminating dead-ending packages. The proposal requires an additional INV element type and provides guidelines for creating minimal packages. Concerns about bandwidth waste in nodes with different policy rules are addressed by suggesting methods like including a hash of the package wtxids in the initial announcement or limiting v1 packages to transactions with few parents. The use of BIP 152 shortids to save bandwidth is discussed, but there are concerns about computational complexity.The concept of transaction packages in Bitcoin is thoroughly explored in the email thread. The proposal aims to propagate incentive-compatible transactions, addressing various questions about multiple pre-signed transactions, the impact of covenants, and transaction rejection due to insufficient fees. The discussion also delves into the potential complexities and challenges of implementing transaction packages, including the creation of minimal packages and the avoidance of predictable orphans. Bandwidth waste, dishonest peer announcements, and the use of BIP 152 shortids are also considered. The participants provide feedback and suggestions, discussing different aspects of the proposal and highlighting the technical details involved in its implementation.In a bitcoin-dev discussion, the Package Relay Proposal is scrutinized, focusing on propagating incentive-compatible transactions despite not meeting the minimum feerate alone. The proposed packaged transaction relay model involves nodes packaging transactions based on peer.feerate and maintaining a transaction DAG with tx.feerate to prevent dead-ending packages. Topological rule concerns in version 1 package relay and potential bandwidth waste from using BIP 152 shortids are brought up. Suggestions to remove fee and weight information from pkginfo, address dishonest peer announcements, and add versioning to individual protocols are discussed. The conversation sheds light on optimizing package relay while minimizing complexity and maintaining network integrity.
Updated on: 2023-08-02T06:45:04.464151+00:00