Coin Brief ENDE

lnd 0.21.8 fixes a reconnect bug that could take every channel to a peer offline

Lightning Labs released lnd v0.21.8-beta on 11 November, together with v0.20.8-beta for the previous line. The release notes for 0.21.8 contain only bug fixes and no database migrations, and two of the changes alter behaviour that operators may notice.

The first is part of a broad pull request that fixes low-level correctness bugs across wire message decoding, watchtower policy, the sweeper, the etcd backend, channel state persistence, gossip validation, channel negotiation and cooperative close. Within it, an etcd transaction now fails when a read inside it fails, instead of going ahead and committing its writes. And a new channel that negotiates a CSV delay of zero is now rejected.

The fix with the widest effect concerns reconnects. If a node reconnected to a peer while a channel's funding transaction was still unconfirmed, lnd remembered the channel but did not send channel_reestablish for it until confirmation. A peer that was waiting for that message would disconnect, and with it every other channel to that peer went offline. lnd now sends the message once on the connection.

Several fixes concern money that is in flight. When publishing a funding batch returns an error, lnd no longer abandons the pending channels or releases their input leases, because the transaction may already have reached the network. The node keeps watching and can recover the channels if the transaction confirms; if it truly cannot be published, the notes say the pending channels currently need manual cleanup. Sweep inputs stay available for retry after unknown or transient mempool rejections, and the sweeper now selects wallet inputs by value per weight, skips coins that cannot pay their own weight at the relay fee rate, and stops before the transaction exceeds the standard weight limit. Settled AMP HTLCs are recovered during on-chain resolution from stored child preimages.

Other fixes reject peer channel aliases already used by another channel, refuse force-close requests for restored channels with no usable commitment transaction, scope confirmation height hints by output script as well as transaction ID, reject oversized unsigned acked update logs instead of truncating them, and remove a deadlock when a link failure overlaps cooperative-close hook registration.

The binaries are reproducible and built with Go 1.27.3, and the manifest and its signature are timestamped with OpenTimestamps.

lnd 0.21.8 fixes a reconnect bug that could take every channel to a peer offline
lnd 0.21.8 fixes a reconnect bug that could take every channel to a peer offline — Coin Brief

Why it matters

None of these is a headline feature, but several touch the paths where a node can lose track of funds or channels: unconfirmed funding, sweeps and force closes. The reconnect fix alone justifies the upgrade for routing nodes with many channels to the same peers.

Written by Victoria Shinder.