-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
sweepremoteclosed can't sweep P2WSH #147
Comments
Can you DM me some of the close transactions in question? I assume they were of type anchor channel? |
Also, what version of The recovery window highly depends on the number of channels opened over the lifetime of the node. 10k might be enough or it might not be. If you want to get a max number, I'd suggest running |
That was it! Updated to latest Huge thanks @guggero |
Woohoo, happy to hear. And sorry about that stupid bug 🙈 |
Fixed by #146. |
We have a number of channels that were in an ABANDONED state due to a (since-fixed) bug in LND v18.0 and LiT.
They have been force-closed on the remote side, and the funds were sent to a a P2WSH address.
I have attempted to use
sweepremoteclosed
with a recovery window as high as 10000, still finding0 sweep targets with total value of 0 satoshis which is below the dust limit of 600
.Have also tried
chantools genimportscript --format electrum --recoverywindow 20000 --lndpaths
and imported private keys into electrum, but unfortunately it only finds channel open/close transactions with P2WPKH outputs.How can I sweep these funds?
The text was updated successfully, but these errors were encountered: