LND fixes bug that could omit settled HTLC records after a node restart
BIBIBI
AT A GLANCE
According to BlockBeats, LND has released a fixed version addressing a counter overflow bug that could omit settled HTLC records after a restart.
Article
Lightning Network node LND fixes bug that omitted settled payments after restart
BlockBeats news, November 17: The developers of the Lightning Network node software LND have fixed a counter overflow bug that could cause nodes to omit records of settled hash time-locked contracts (HTLCs) after a restart. The fix code was merged on November 5, and LND released version v0.21.8-beta containing the fix on November 11.
The developers explained that the 16-bit counter used to record the number of remotely confirmed update entries resets to zero upon reaching 65,536 entries, and after a node restart the update list may be read as empty. The fix measures include rejecting overly long lists and restoring old records when validation conditions are met.
BlockBeats reported on November 17 that LND developers have fixed a counter overflow bug.
02
The bug could cause nodes to omit records of settled hash time-locked contracts (HTLCs) after a restart.
03
The fix code was merged on November 5, and version v0.21.8-beta containing the fix was released on November 11.
04
The developers explained that the 16-bit counter recording the number of remotely confirmed update entries resets to zero upon reaching 65,536 entries, and after a node restart the update list may be read as empty.
05
The fix measures include rejecting overly long lists and restoring old records when validation conditions are met.
AI-assisted interpretation
The following is analysis, separate from reported facts. Verify important claims independently.
The problem lies in the counter that records the number of updates: upon reaching 65,536 entries, it resets to zero, which may cause the node to treat the update list as an empty list after a restart and omit settled records. The fix described in the report rejects overly long lists and restores old records when validation conditions are met; it does not unconditionally restore all records.
Why it matters to readers
The bug concerns whether settled records can be correctly read after a node restart. The report has given the version containing the fix, but does not state the actual scope of impact or the status of fix deployment.
It is necessary to distinguish between "omitting settled records" and "confirmed loss of funds": the original text only states the possibility of the former and does not report any loss of funds. If you run a node using LND, you can pay attention to the version containing the fix and whether your own version is affected.
Risks and unknowns
The original text does not specify the range of affected versions.
The original text does not state whether exploitation of the bug or actual loss of funds occurred.
The original text does not provide independent verification results on the effectiveness of the fix, nor does it describe the status of node upgrade deployment.
Restoration of old records requires meeting validation conditions; the original text does not give the specific conditions or the scope of restoration.
Related Developments
Loading event timeline…
Related concepts
Hash time-locked contract (HTLC)
This term is not in the glossary yet. Browse related concepts in the glossary.