Coins Lightning
Menu

LND fix addresses channel-record overflow that could affect accounting after a restart

As reported on November 17, 2026, Lightning developers had fixed a flaw in LND, a Lightning node implementation, that could cause a node to misread channel records after restarting. ChainCatcher, citing CryptoSlate, said a 16-bit counter used when saving and restoring channel updates could wrap to zero at 65,536 entries. The node could then read the record as an empty list and omit settled hashed timelock contracts (HTLCs), undermining the payment channel’s accounting integrity.

Developers said a connected node could drive the entry count toward that limit by repeatedly sending transaction-fee updates and commitment signatures while withholding required revocation messages.

LND released v0.21.8-beta and v0.2.8-beta on November 11, adding a safeguard when writing records and checks when loading older records. It had not been confirmed whether the flaw was exploited or caused any loss of funds.