0 sats \ 2 replies \ @BTC_LN 27 Jan \ on: The Guide where your Lightning close-transaction can't get the channel closed lightning
Great writeup! You helped me resolve two channels closures that were pending for a long time.
What if I have force closed channels that are still showing as pending in Thunderhub, even though they are confirmed and many weeks or even months old? How can I force LND to recognize them as closed channels? I did try to restart LND. Do you have any recommendation?
Glad that you got your 2 channel closures resolved!
The two in Thunderhub, are they showing up in
lncli pendingchannels? What might also be is that there are anchors of those channels still pending, or more likely they got stolen and your LND didn't notice it. You could identify missing anchors as the 330sat sweeps still pending at lncli wallet pendingsweeps. If it's anchors, you may see those 330 sat not at limbo, but stolen.To mitigate, you have 3 choices:
- just ignore them
- if they are not stolen: force-collect those anchor sats. In the current fee-environment, this is going to be unprofitable. Hence LND doesn't autosweep them, since it's not making any sense economically. But you could RBF the anchor transaction up to like 25sats/vbyte now and
--forcethe bump (like in Solution 6 above) - if they are stolen: try broadcasting the raw-tx of the anchor-tx (like in Solution 5 above). Best case, your LND will notice that those anchors are stolen and they'll disappear from your pendingsweeps list