Bitcoin Lightning developers patch bug that could make completed payments disappear

LND's November 11 releases prevent a specific update-log overflow from omitting settled HTLCs when channel state is rebuilt. Read the full story on CryptoSlateUnderstand the crypto stories that matter and what to watch next. Get The Catalyst in your inbox

Bitcoin Lightning developers patch bug that could make completed payments disappear

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.21.8-beta and v0.20.8-beta on Nov. 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.

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.

The vulnerability became more concerning after developers identified a potential way for connected peers to push the affected update list toward its limit.

Originally published by cryptoslate Aggregated for informational purposes. All rights belong to the original publisher.
← Back to all news