Bitcoin Lightning Developers Fix Bug That Could Cause Completed Payments to Disappear

iconCryptoSlate
Share
AI summary iconSummary
Bitcoin breaking news: Bitcoin Lightning developers have fixed a bug in LND that could erase settled payment records after node restarts. The flaw involved a 16-bit counter for peer updates, leading to incomplete HTLC records. The fix was released in v0.21.8-beta and v0.20.8-beta on Nov. 11, 2026. The patch was merged on Nov. 5. The issue could occur if a peer sent repeated updates without revocation messages, causing the counter to overflow. Developers added checks to block oversized update lists and recover valid data. No confirmed exploits or losses have been reported. Bitcoin news shows the network remains under active maintenance.

Bitcoin Lightning developers fixed a vulnerability in LND that could leave nodes with incomplete records of settled payments after restarting. The failure could occur even with the original payment information still on disk. Incomplete records could disrupt the accounting that channel participants use to establish settled payments and amounts owed.

LND is a widely used implementation of Bitcoin's Lightning Network. The network allows users to transfer Bitcoin through payment channels without placing each transaction directly on the blockchain. Developers issued versions v0.21.8-beta and v0.20.8-beta on Nov. 11 to fix an error in saving and restoring channel updates. The fix entered LND's main development branch on Nov. 5, ahead of both November releases.

LND maintainer Olaoluwa Osuntokun, also known as Roasbeef, said the problem concerned a counter for acknowledged updates from a connected Lightning peer. LND used a 16-bit unsigned integer to store the entry count, limiting the counter to 65,535. A list reaching 65,536 entries caused the counter to return to zero while LND kept saving updates. After a restart, a node could read the zero as indicating no entries and leave out a settled hashed timelock contract (HTLC). An HTLC is a conditional payment mechanism that helps protect transactions across Lightning channels.

LND collaborator ziggie1984 explained in a GitHub discussion that a peer could repeatedly transmit transaction fee updates and commitment signatures without sending a required revocation message. That behavior let pending acknowledgments accumulate without clearing the list. The developer demonstrated the behavior in a unit test that produced 201 stored updates from 200 message rounds. The entries persisted across reconnections, suggesting repeated disconnections and reconnections would not necessarily stop the list from reaching the overflow threshold.

Developers added checks to block oversized update lists from moving channel state forward or entering storage. Developers also changed record reading so nodes can recover complete update lists stored by earlier versions, provided the underlying data passes validation. However, the project's disclosures identify no confirmed exploitation or financial losses linked to the vulnerability. Whether any live nodes encountered the flaw before the patch remains unknown.

Disclaimer: The information on this page may have been obtained from third parties and does not necessarily reflect the views or opinions of KuCoin. This content is provided for general informational purposes only, without any representation or warranty of any kind, nor shall it be construed as financial or investment advice. KuCoin shall not be liable for any errors or omissions, or for any outcomes resulting from the use of this information. Investments in digital assets can be risky. Please carefully evaluate the risks of a product and your risk tolerance based on your own financial circumstances. For more information, please refer to our Terms of Use and Risk Disclosure.