V3 transaction policy for anti-pinning

V3 transaction policy for anti-pinning

Original Postby instagibbs

Posted on: January 9, 2024 14:57 UTC

The discussion focuses on the intricacies of determining an appropriate pin size in relation to mempool conditions, referencing a Bitcoin Improvement Proposal (BIP) which suggests a maximum "5x theoretical pin." This maximum is a significant reduction from the previously stated 500x, although it acknowledges that practical limits will vary based on factors often beyond the control of both attackers and defenders in the network.

The proposal implies that the only direct method for further reducing this pin size would be to decrease the Child-Pays-For-Parent (CPFP) maximum size, with the caveat of not affecting legitimate CPFP transactions.

Previously, the child transaction size was around 4kvB, but adjustments have already been made once after discussions. To aid in understanding and potentially to contribute to more informed decisions regarding these sizes, @0xB10C has created visual representations in the form of charts. These charts illustrate relevant data and can be found shared on social media, specifically Twitter, providing a resource for those interested in the technical details of the BIP's considerations. The information shared in the provided GitHub link to the BIP text gives a more detailed explanation of the motivation behind these proposals and the implications for Bitcoin's transaction processes.