U-got-IT
commented
2 months ago Update: after some reading I was able to find the raw closing transaction and post it manually. The channel has now closed and the funds are now recovered.
However, I had to post the transaction directly to bitcoind. lightning-cli sendrawtransaction failed with the error message "dust". Could this have been the problem all along? Here is the transaction id in question:
cb47a00fc264d3e0d59fa93c9ed09be24e4aa44e26672301f35e85c38f0fbc22
Issue and Steps to Reproduce
My LND peer had a hardware crash and lost its channel state. Recovery on their end failed according to them. They cannot trigger a force close. The problem is that I cannot do anything from my side either even though I must have all the correct information in my database.
The state from listpeerchannels is:
"state_changes": [ { "timestamp": "2024-09-11T02:52:15.692Z", "old_state": "CHANNELD_NORMAL", "new_state": "AWAITING_UNILATERAL", "cause": "remote", "message": "They sent ERROR channel 06765c3ae87d07723ce413f6b2fc28c172a37427cc864649e762eeaf1b575217: unable to resume channel, recovery required" } ],
When I try to (force) close from my side I get:
lightning-cli close 10
{
"code": -32602,
"message": "id: Channel in state AWAITING_UNILATERAL: invalid token '\"\"'"
}
lightning-cli close 10
{
"code": -1,
"message": "Peer has no active channel"
}
There must be a way to force unilateral payout from my end, right?
getinfooutput"version": "v24.08",