Deep Web3

SYSTEMS.
PEOPLE.
POSSIBILITIES.

Menu

Go beneath
the surface.

LND Fixes Channel-Record Counter Overflow That Could Affect Accounting After Restart

As reported on November 17, 2026, Lightning Network developers had fixed a bug in LND that could cause a node to misread payment-channel records after a restart. ChainCatcher, citing CryptoSlate, reported that exploitation and any resulting loss of funds remained unconfirmed.

The issue lay in how LND saved and restored channel updates. A 16-bit counter tracking the number of entries would wrap to zero at 65,536. After a restart, the node could then interpret the record as an empty list and omit settled hashed timelock contracts (HTLCs), undermining the integrity of its channel accounting.

According to developers, a connected peer could drive the entry count toward that limit by repeatedly sending fee updates and commitment signatures while withholding the required revocation messages. LND released v0.21.8-beta and v0.2.8-beta on November 11, 2026, adding protections when writing records and checks when loading older records.