You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I closed a channel using lightning-cli close but the terminal froze,
I tried a second time and the channel did a unilateral close.
Looking at listclosedchannels, the close_cause shows "protocol" and the last_commitment_id: 282e3f8b7a923d48817e49167b753b04b11ea3f8b5f1c11dc214933e33334e7f
From the mempool explorer, I then follow the next transaction, which shows the force-closed txID: 95c2136c14dac55e1898086f0744b0f3fbf4d54eaf0ae8d24dec820f35ce8272
I can track both of those transactions in listtransactions but none shows in my listfunds.
How can I recover the funds?
transactions are confirmed and should show up in your cln wallet. If they are really missing, I would first try with lightning-cli dev-rescan-outputs. If they are still missing you could try to launch lightningd with --rescan=-848273 (one block before the transaction that sent the funds to your wallet was mined).
It worked!!
I first tried lightning-cli dev-rescan-outputs but it did not reveal the tansaction.
Then I restarted lightningd with --rescan=-848273 and BOUM the transaction appeared in the listfunds.
Thank you very much, should we close this issue or should this be tracked as a bug?
Issue and Steps to Reproduce
I closed a channel using
lightning-cli close
but the terminal froze,I tried a second time and the channel did a unilateral close.
Looking at listclosedchannels, the close_cause shows "protocol" and the last_commitment_id:
282e3f8b7a923d48817e49167b753b04b11ea3f8b5f1c11dc214933e33334e7f
From the mempool explorer, I then follow the next transaction, which shows the force-closed txID:
95c2136c14dac55e1898086f0744b0f3fbf4d54eaf0ae8d24dec820f35ce8272
I can track both of those transactions in listtransactions but none shows in my listfunds.
How can I recover the funds?
getinfo
outputlistclosedchannels
outputlisttransactions
for both close attemptsThe text was updated successfully, but these errors were encountered: