Bitcoin Lightning developers patch bug that could make completed payments disappear
Image by Lightning BTC 0.80% · 24h Bitcoin Lightning developers patch bug that could make completed payments disappearA software flaw could cause nodes to lose track of settled payment updates after restarting,...
Bitcoin 1 Minute
Here is the latest from the digital-asset markets: Image by Lightning BTC 0. 80% · 24h Bitcoin Lightning developers patch bug that could make completed payments disappearA software flaw could cause nodes to lose track of settled payment updates after restarting, threatening the integrity of Lightning channel records. By Oluwapelumi Adejumo Senior Reporter Nov.
16, 2026 at 10:10 pm GMT 2 min read Quick Take 01 Bitcoin Lightning developers patched an LND vulnerability that could cause nodes to lose track of settled payment records after restarting. 02 The flaw caused a software counter to reset at 65,536 entries, potentially disrupting payment-channel accounting and the accuracy of settlement records. 03 Developers identified a way peers could trigger the overflow, but whether any live nodes encountered the bug before the patch remains unknown.
Market Dynamics
Make preferred on Share Share Bitcoin Lightning developers patched a software vulnerability that could cause nodes to lose track of settled payments after a restart, potentially disrupting the accounting records that secure payment channels. The flaw affected LND, a widely used implementation of Bitcoin's Lightning Network, which enables users to send Bitcoin through payment channels without recording every transaction directly on the blockchain. Developers released v0.
11 to address the issue, which stemmed from an error in how the software saved and restored channel updates. The vulnerability could cause a node to reconstruct incomplete payment records after restarting, even when the original information remained stored on its disk. That failure threatened the consistency of Lightning channels, where participants rely on accurate records to determine which payments have settled and what each party is owed.
According to LND maintainer Olaoluwa Osuntokun, known as Roasbeef, the problem involved a counter that tracked acknowledged updates from a connected Lightning peer. The software stored the number of entries using a 16-bit unsigned integer, which can represent values only up to 65,535. Once the list reached 65,536 entries, the counter reset to zero, even though LND continued writing the updates to storage.
Market Impact
Upon restarting, the node could interpret that zero as an empty list and omit a previously settled hashed timelock contract (HTLC), a conditional payment mechanism that helps secure transactions across Lightning channels. Why written updates could be missing after restartAt 65,536 log entries, LND's old stored count could wrap to zero. The released patch adds write guards and checks older records on load.
Choose the record pathChoose the record pathNew writesOlder recordsOversized lists are rejected before commitment progress or revocation, and before serialization writes record bytes. The updated reader validates entries and count. It can recover qualifying complete lists; malformed trailing data is rejected.
This shift continues to shape the digital-asset landscape, with analysts examining its near-term effects.





