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
Describe the bug
After closing all channels and transactions have confirmed. Attempting to sweep funds to cold storage does not work. UTXOs are reserved or short?
To Reproduce
Using RTL webUI or raspiblitz webUI or the bitcoin-cli send shell command to send/sweep funds results in these error messages:
Expected behavior
Expected that after channels are closed (and 4000+ blocks later after confirmation) that I would be able to continue to use/spend the satoshis in main chain wallet.
Desktop (please complete the following information):
OS: macOS/Linux
LN implementation: CoreLightning
Platform: Raspiblitz
Additional context
None
The text was updated successfully, but these errors were encountered:
First of all ... your on-chain wallet is also handled by your lightnig client - not bitcoind. So this also is not a raspiblitz error to open an issue on but some user experience with LND or CoreLightning over RTL. Best would be to ask for support in channel & funds management in the Telegram Community Groups: https://t.me/raspiblitz
I'll reopen this. While this is actually a CLN problem, we should display a more helpful message to the user. This means we do a bad job at detecting this state.
Describe the bug
After closing all channels and transactions have confirmed. Attempting to sweep funds to cold storage does not work. UTXOs are reserved or short?
To Reproduce
Using RTL webUI or raspiblitz webUI or the
bitcoin-cli send
shell command to send/sweep funds results in these error messages:Expected behavior
Expected that after channels are closed (and 4000+ blocks later after confirmation) that I would be able to continue to use/spend the satoshis in main chain wallet.
Desktop (please complete the following information):
Additional context
None
The text was updated successfully, but these errors were encountered: