That is an opinion editorial by Shinobi, a self-taught educator within the Bitcoin area and tech-oriented Bitcoin podcast host.

For the second time in roughly a month, btcd/LND have had a bug exploited which triggered them to deviate in consensus from Bitcoin Core. As soon as once more, Burak was the developer who triggered this vulnerability — this time it was clearly intentional — and as soon as once more, it was a problem with code for parsing Bitcoin transactions above the consensus layer. As I mentioned in my piece on the prior bug that Burak triggered, earlier than Taproot there have been limits on how giant the script and witness knowledge in a transaction may very well be. With the activation of Taproot, these limits had been eliminated leaving solely the constraints on the block dimension restrict itself to restrict these elements of particular person transactions. The issue with the final bug was that although the consensus code in btcd was correctly upgraded to mirror this modification, the code dealing with peer-to-peer transmission — together with parsing knowledge earlier than sending or when receiving — didn’t correctly improve. So the code processing blocks and transactions earlier than it truly bought handed off to be validated for consensus failed the information, by no means handed it to the consensus validation logic and the block in query didn’t ever be validated.

Source link