Thanks to @justin_shocknet help on my previous post, I was able to understand that the channels are in a
ChanStatusRestored, this usually happens when a channel has been restored from a backup that did not match the current status of the channels in the peer node.The good news on this is that in this case the error does not contain the flag
ChanStatusLocalDataLoss assuming that the data about this channel (ie: % of liquidity on my side or the peer side) is still available. Not sure how to retrieve it yet, but it will be useful to know when proceeding to the next step.Since my last post I was able to:
-
successfully connect with all three peers the node share the channels with, and ask them to close or force close the channels in their side. Two channels have been closed and the sats have returned to the onchain wallet with the amount shown in their latest channel state.
-
Unfortunately, with one of the peers, the one where the opening transaction was never confirmed in the blockchain, we still discussing how it's possible that this happened, here below the last received response:
I used RTL. I can't see you as a peer atm. Also I can't find us ever being connected in the past (which is weird). Also I can't close or pump my attempt to open a channel between us, using bump or cancel in RTL. I guess because it is too old and canceled therefore. In my local memepool it can't find the transaction and status: waiting till it will appear in memepool.
then, also added this:
Opening Channel Information Capacity: 3,000,000 Confirmation Height: Local Balance: 2,996,530 Remote Balance: 0 Fee/KW: 2,500 Commit Weight: 772 Commit Fee: 2,810
So I assume he is able to see the channel information that I'm unable to retrieve. Considering that we did not yet used
chantools, I wonder what will be the right thing to do next, also considering there's zero sats on my side? Is this knda zombiechannel affecting the network or I should just don't care and let the peer figure out the way to fix it on its node side?FYI: @DarthCoin