Great Consensus Cleanup Revival
Posted by evoskuil
Aug 26, 2024/17:33 UTC
The discussion revolves around the proposed approach to invalidate 64 byte transactions within a blockchain or similar system, which has sparked significant debate regarding its effectiveness and implications. This proposal is not aimed at addressing any known vulnerability, contrary to what some might suggest. It's important to understand that blocks with valid transactions inherently do not suffer from malleable block hashes, indicating that the issue this proposal aims to tackle might not be as critical as presented.
Moreover, the method suggested for mitigating what is known as the invalid block hash caching weakness introduces unnecessary complexity and incurs higher costs compared to existing solutions. The argument against the utility of caching invalid messages as a means to optimize against Denial of Service (DoS) attacks is substantial, highlighting that such practices may, in reality, be counterproductive.
From a consensus perspective, implementing a rule to invalidate these transactions seems redundant and likely to introduce more problems than it solves. It demands additional validation checks that are not essential to the system's operation, thereby complicating the process without clear benefits. Although there might be a case for considering this move as an optimization technique for Simplified Payment Verification (SPV) bandwidth, it's crucial to steer clear of misrepresenting the measure as a remedy for a flaw within the system.
TLDR
Join Our Newsletter
We’ll email you summaries of the latest discussions from authoritative bitcoin sources, like bitcoin-dev, lightning-dev, and Delving Bitcoin.
Explore all Products
We'd love to hear your feedback on this project?
Give Feedback