A Lightning node needs to recover its payment-channel records accurately after a restart. As reported on November 17, 2026, citing CryptoSlate, LND developers had fixed a flaw that could cause a node to misread saved channel updates and omit settled hashed timelock contracts (HTLCs) from its records.
The problem involved a 16-bit counter used to store the number of entries in a channel-update record. At 65,536 entries, the counter would wrap to zero. After a restart, the node could then read the record as an empty list, undermining the channel’s accounting integrity.
Developers said a connected node could drive the entry count toward that limit by repeatedly sending fee updates and commitment signatures while withholding required revocation messages. LND released v0.21.8-beta and v0.20.8-beta on November 11, 2026. The fixes add a safeguard when writing records and validate older records when loading them.
For anyone operating an LND node, the practical check is whether it runs one of those fixed versions. The report describes a potential failure mode; it does not establish that funds were lost.