Skip to content
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

Unable to sweep funds, UTXOs are short or reserved? #231

Open
nomo-nomad opened this issue Nov 12, 2023 · 2 comments
Open

Unable to sweep funds, UTXOs are short or reserved? #231

nomo-nomad opened this issue Nov 12, 2023 · 2 comments
Assignees
Labels
enhancement New feature or request investigate Every issue that requires further investigation
Milestone

Comments

@nomo-nomad
Copy link

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:
Screenshot 2023-11-12 at 7 37 16 AM
Screenshot 2023-11-12 at 1 32 52 PM

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

@rootzoll
Copy link
Collaborator

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

@fusion44 fusion44 reopened this Nov 14, 2023
@fusion44
Copy link
Owner

fusion44 commented Nov 14, 2023

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.

@fusion44 fusion44 self-assigned this Nov 14, 2023
@fusion44 fusion44 added enhancement New feature or request investigate Every issue that requires further investigation labels Nov 14, 2023
@fusion44 fusion44 added this to the v0.7.0-beta milestone Nov 14, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request investigate Every issue that requires further investigation
Projects
None yet
Development

No branches or pull requests

3 participants