LND 0.21.4 changes new channel handling and fixes payment edge cases

An update for Lightning operators

LND published version 0.21.4-beta on October 1. Its official release page says there are no database migrations and provides signed manifests, binary checksums and reproducible-build instructions. Operators can use those materials to verify that a downloaded package corresponds to the published release.

The change affects software running Lightning payment channels. It does not alter Bitcoin’s block rewards or establish a new on-chain fee schedule.

What changes at the channel boundary

The versioned release notes say LND will no longer open or accept new channels using the legacy commitment type. Existing channels of that type remain usable, including their normal closing paths. Newly negotiated channels use an explicit channel type.

Other fixes address payments left pending during channel transitions, replay handling in forward interception and failures involving reusable AMP invoices. The notes also describe stricter invoice decoding when multiple payment-hash fields appear.

For operators and wallet developers, the practical task is to check channel-opening and invoice integrations against the documented behavior. These changes should not be read as a guarantee that every attempted payment will succeed: routing and peer conditions remain part of the payment flow. Users of hosted Lightning services can ask which implementation and version their provider operates.