limbo balance not recovered after local force close

[nixonrichard1971]

LND version: v0.16.2-beta

Issue: After a local force close of a channel (initiated by my node, possibly due to HTLCs?) which tx was confirmed >2weeks, one of the outputs is locked as "limbo balance" and my node is now creating lots of sweeps making many of my utxo's show as unconfirmed.

When i run the command lncli pendingchannels I get the pending close channel as output and the weird thing is that in anchor the result shows "LOST".

Any ideas on how to solve this? I have seen other discussions but I don't see this one matching any other.

[nixonrichard1971]

hi, any thoughts on this item, please? thank you

[nixonrichard1971]

hi, thanks. I've tried two times with these inputs but it didn't seem to find the correct keys locally. First time it went over 240keys and the pc went to sleep and I am not sure if it went over all of them because my pc connection to the node broke with the pc going to sleep. The second time it went over the 500 key iteration and didn't find the correct keys (target script not derived). do I need to tweak any of the other parameters?

[guggero]

Yes, you probably need to tweak some parameters. Can you tell me what the RemoteChanCfg -> RevocationBasePoint -> Path value is for the channel (when running chantools dumpbackup)? And how old was the channel approximately? And was it very active (a lot of forwards or re-balances)?

[nixonrichard1971]

The path is "m/1017'/0'/0'/0/0" and the channel funding tx was confirmed 4months ago. The channel was not very active.

[guggero]

The path is "m/1017'/0'/0'/0/0"

Sorry, my mistake. The remote path is always all zeroes at the end... What's the path for the local one is what we need to know in this case.

[nixonrichard1971]

the LocalChanCfg -> RevocationBasePoint -> Path is "m/1017'/0'/1'/0/170"

[guggero]

Okay, can you try with the following additional parameters (keep everything else as before): --maxnumchanstotal=171 --maxnumchanupdates=5000.

If that doesn't work, then it's possible the other side closed the channel (hard to say from just the transaction itself). In that case it would be worth trying out chantools sweepremoteclosed --recoverywindow 1000 --feerate 15 --sweepaddr <address_from_your_wallet_to_send_funds_to>.

By the way, both these commands can be run on your computer as well, which might be faster. All you need is the correct binary for your operating system and the seed.

[nixonrichard1971]

thanks. For the first one with the additional parameters, it stopped at 171 keys and then threw and error:

2023-09-04 22:04:00.744 [INF] CHAN: Tried 171 of 500 keys. Error: target script not derived

Prior to the reset-wallet-transactions I could see in Thunderhub that the channel was force closed locally (however i did not force-close it). do you think is possible that LND got confused with who closed this channel? I'll try and let you know if this solved the problem.

[nixonrichard1971]

Hi, just getting back with this one. The second script chantools sweepremoteclosed was run and it found one unspent output for one address (not the one we're looking for) and threw me this output:

2023-09-05 06:33:52.233 [INF] CHAN: Found 1 unspent outputs for address bc1qx3eyqqeucqwv84h65rzgnxtg8u0tmew4zpa9f0
2023-09-05 06:40:00.010 [INF] CHAN: Fee 1646 sats of 2680444 total amount (estimated weight 439)
2023-09-05 06:40:00.012 [INF] CHAN: Transaction: 02000000000101226d5cd84a56f5314323f35f259680b835897b45c23a209434f5c46f519de1e10100000000ffffffff010ee0280000000000160014608af4b83b932d0274e6421aeee3e4d337a0be0e024730440220169361474d236e955d21a20e226659547063ece74d88f9408e560e1ba06a977602206fb8a988545956e7a1e39975be1a4568bcfdbe63ffc9523245ceb585b386db86012102da2713e494de094a2cafac68a4d5ac2ac1ab51fd15673c47b6d660bf3652cf6d00000000

If I look for the address bc1qx3eyqqeucqwv84h65rzgnxtg8u0tmew4zpa9f0 (not the one we were concerned here anyway) the output has not been spent, so I am not sure if the tx has been published? FYI, now that I think of it I did not add --publish in this command (because I just copied your command above) so that might be why it did not publish it? But anyway, this seems to be a 3M sats channel that my peer has closed remotely possibly because I've been offline for too long already, and not the channel of 10M sats I'm having the issue with (lost anchor).

So, to sum up, I think the problem is still there. The wallet is stuck loading in the same place, the output of the 10M sat channel in limbo is still locked in the address. If I run lncli pendingchannels the output is:

[lncli] rpc error: code = Unknown desc = unable to find arbitrator

Appreciate the help and the patience with this one, it's a tricky one.

[guggero]

No, if you don't specify --publish, it won't be published. But you can copy the transaction hex string and publish it manually on a block explorer.

Hmm, so yeah, if Thunderhub said it was a local force close, then sweeptimelockmanual is the correct one.
Would you mind sending me the full output of chantools dumpbackup (just for this specific channel) and the exact parameters you use for sweeptimelockmanual currently? You can also DM me the info on Slack or Keybase (same username) if you want.