Skip to main content
Bitcoin Lightning developers patch bug that could make completed payments disappear

Bitcoin Lightning developers patch bug that could make completed payments disappear

CryptoSlate
16 lis 2026, 22:14Cryptoslate
Oryginał
2 min read

Bitcoin Lightning developers patched a vulnerability in LND that could cause nodes to lose track of settled payments after restarting, potentially disrupting payment-channel accounting.

The flaw affected how the software saved and restored channel updates, potentially causing nodes to reconstruct incomplete payment records after restarting. This threatened the consistency of Lightning channels, where participants rely on accurate records to determine settled payments and channel obligations.

Technical Details

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.

The software stored the number of entries using a 16-bit unsigned integer, which can represent values only up to 65,535.

Olaoluwa Osuntokun, LND maintainer

Once the list reached 65,536 entries, the counter reset to zero, even though LND continued writing the updates to storage. 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.

Potential Exploitation

The vulnerability became more concerning after developers identified a potential way for connected peers to trigger the flaw. LND collaborator ziggie1984 explained that a peer could repeatedly send transaction fee updates and commitment signatures while withholding a required revocation message, allowing the list of pending acknowledgments to grow without being cleared.

The developer reproduced the behavior in a unit test, generating 201 stored updates after 200 rounds of messages. Crucially, the accumulated entries survived reconnects, suggesting that repeatedly disconnecting and reconnecting would not necessarily prevent the list from eventually reaching the overflow threshold.

Solution Released

To address the problem, developers introduced checks that prevent oversized update lists from advancing the channel state or being written to storage. They also modified how LND reads existing records, allowing nodes to recover complete update lists saved by older versions when the underlying data passes validation.

The fix was merged into LND's main development branch on November 5 before being included in both November releases. The project's disclosures do not identify any confirmed exploitation or financial losses associated with the flaw.

Z.ai
Article written by AI
Z.ai GLM-4.5-FlashFree
Free AI articles150 of 150
No limit after signing in with Telegram