[bug]: ChanStatusBorked|ChanStatusCommitBroadcasted|ChanStatusLocalCloseInitiator - LND is not recovering limbo balance

[TheDarkLight21]

Background

I had a channel close that I'm assuming is a FC, although, it did not show up as FC in my bos_telegram bot. Channel is still pending close. Current lncli pendingchannels returns:

{ "total_limbo_balance": "1531294", "pending_open_channels": [ ], "pending_closing_channels": [ ], "pending_force_closing_channels": [ ], "waiting_close_channels": [ { "channel": { "remote_node_pub": "0298f6074a454a1f5345cb2a7c6f9fce206cd0bf675d177cdbf0ca7508dd28852f", "channel_point": "383c3251192d4eac10efdd972699b3b32c2872c336a0c58b1f75c3438384455c:2", "capacity": "2000000", "local_balance": "1531294", "remote_balance": "468505", "local_chan_reserve_sat": "20000", "remote_chan_reserve_sat": "20000", "initiator": "INITIATOR_REMOTE", "commitment_type": "STATIC_REMOTE_KEY", "num_forwarding_packages": "7", "chan_status_flags": "ChanStatusBorked|ChanStatusCommitBroadcasted|ChanStatusLocalCloseInitiator", "private": false }, "limbo_balance": "1531294", "commitments": { "local_txid": "ec918cd6ba408a5ea66074155c330895943fae30510df6796060c17023e31a35", "remote_txid": "dc15c969e79a096555a9c8561fc1ccb8b357df18868680cc0c572f388454e47a", "remote_pending_txid": "", "local_commit_fee_sat": "200", "remote_commit_fee_sat": "200", "remote_pending_commit_fee_sat": "0" }, "closing_txid": "ec918cd6ba408a5ea66074155c330895943fae30510df6796060c17023e31a35" } ] }

The on-chain fee is set so low I'm thinking this will never confirm, but also unsure what I may need to do to recover funds on my side with the ChanStatusBorked flag.

grep of the lnd.log file for the remote node's pubkey shows the following just looping every so often:

2023-10-05 23:56:09.495 [INF] SRVR: Established connection to: 0298f6074a454a1f5345cb2a7c6f9fce206cd0bf675d177cdbf0ca7508dd28852f@174.169.193.33:9735 2023-10-05 23:56:09.501 [INF] SRVR: Finalizing connection to 0298f6074a454a1f5345cb2a7c6f9fce206cd0bf675d177cdbf0ca7508dd28852f@174.169.193.33:9735, inbound=false 2023-10-05 23:56:09.823 [INF] PEER: Peer(0298f6074a454a1f5345cb2a7c6f9fce206cd0bf675d177cdbf0ca7508dd28852f): Loading ChannelPoint(383c3251192d4eac10efdd972699b3b32c2872c336a0c58b1f75c3438384455c:2), isPending=false 2023-10-05 23:56:09.824 [WRN] PEER: Peer(0298f6074a454a1f5345cb2a7c6f9fce206cd0bf675d177cdbf0ca7508dd28852f): ChannelPoint(383c3251192d4eac10efdd972699b3b32c2872c336a0c58b1f75c3438384455c:2) has status ChanStatusBorked|ChanStatusCommitBroadcasted|ChanStatusLocalCloseInitiator, won't start. 2023-10-05 23:56:09.824 [INF] PEER: Peer(0298f6074a454a1f5345cb2a7c6f9fce206cd0bf675d177cdbf0ca7508dd28852f): Negotiated chan series queries 2023-10-05 23:56:09.824 [INF] DISC: Creating new GossipSyncer for peer=0298f6074a454a1f5345cb2a7c6f9fce206cd0bf675d177cdbf0ca7508dd28852f 2023-10-05 23:56:09.828 [INF] PEER: Peer(0298f6074a454a1f5345cb2a7c6f9fce206cd0bf675d177cdbf0ca7508dd28852f): Sending 1 channel sync messages to peer after loading active channels 2023-10-05 23:56:10.131 [INF] PEER: Peer(0298f6074a454a1f5345cb2a7c6f9fce206cd0bf675d177cdbf0ca7508dd28852f): unable to read message from peer: EOF 2023-10-05 23:56:10.132 [INF] PEER: Peer(0298f6074a454a1f5345cb2a7c6f9fce206cd0bf675d177cdbf0ca7508dd28852f): disconnecting 0298f6074a454a1f5345cb2a7c6f9fce206cd0bf675d177cdbf0ca7508dd28852f@174.169.193.33:9735, reason: read handler closed

No database corruption to my knowledge and all other channels are functioning normally.
Initially, maybe 5 hours after I rec'd the chan close notification in bos bot the local/close txid was showing in the mempool and it also showed up as pending receive in my on-chain wallet. At that time I could also see it with lncli listchaintxns however, I recall seeing "is_our_address": false, for both the local balance and the remote balance.

At the present, the local/close txid is no longer in the mempool and as such I can no longer see a pending received in my on-chain wallet. The on-chain fee for the remote txid is set super low at 1.12 sat/vB. I'm assuming it'll eventually drop out of the mempool when it ends up not confirming so not sure what I can do on my end to recover these funds.

Your environment

• LND: v0.16.4-beta
• Linux 5.10.103-v8+ aarch64
• bitcoind --version: Bitcoin Core version v25.0.0
• any other relevant environment details

Steps to reproduce

Channel close with "chan_status_flags": "ChanStatusBorked|ChanStatusCommitBroadcasted|ChanStatusLocalCloseInitiator"

Expected behaviour

Limbo Balance to return to my on-chain wallet or show some sign or block height when the local balance will return

Actual behaviour

Channel with flag ChanStatusBorked fail to claim limbo funds to wallet

[hieblmi]

Thanks for your report @TheDarkLight21, I think this is a similar discussion like the one here: #8061 (comment)