[ad_1]
Watch This Episode On YouTube Or Rumble
Hear To The Episode Right here:
On this episode of “Bitcoin, Defined,” hosts Aaron van Wirdum and Sjors Provoost focus on a latest bug within the btcd Bitcoin implementation that affected a big a part of the Lightning Community, because it disconnected LND Lightning nodes from the Bitcoin blockchain.
Within the episode, van Wirdum and Provoost clarify {that a} developer going by the identify Burak on Twitter created a 998-of-999 multisig transaction by leveraging the latest Taproot improve. Though this was a legitimate transaction, btcd and LND nodes rejected it, and subsequently rejected the block that included the transaction and all blocks that got here after it. Lightning Labs launched a patch that very same night to repair the difficulty with LND nodes.
Particularly, Provoost explains, btcd rejected the transaction as a result of it has a most restrict on how a lot witness information a Segwit transaction can embody. Though different Bitcoin implementations do implement this restrict on Segwit model 0 transactions, Segwit model 1 (that’s, Taproot) transactions haven’t any such restrict. This discrepancy is what appears to have prompted the difficulty within the btcd implementation.
Nonetheless, it’s a bit unclear why this bug in btcd seemingly additionally affected many LND Lightning nodes which use Bitcoin Core relatively than btcd to validate blocks. Within the second half of this week’s episode, Provoost speculates how the 2 could also be linked.
To conclude the episode, van Wirdum and Provoost clarify how the Lightning Community is affected when Lightning nodes reject the Bitcoin blockchain.
[ad_2]
Source link
