-
Notifications
You must be signed in to change notification settings - Fork 943
Currently waiting on previous splice command to finish #6656
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
Comments
Some splice messages:
|
After restarting the node, I also tried splicing out more than the dust limit, with the same peer:
|
I also tried splicing in. Because
(using the v2 support PR bitcoin/bitcoin#21283). And then: This ended up stuck. From the log:
|
That last action seems to have resulted in a unilateral close from their end, which they deny having done themselves :-):
|
Logs from their end (running v23.08):
|
cc @ddustin |
I believe this may be caused because the PSBT didn't provide an output to receive the outgoing funds and the error handling around that isn't giving the appropriate error 👀. Going to investigate this possibility. |
Thanks again for the report!
|
Uh oh!
There was an error while loading. Please reload this page.
Using CLN v23.08.
I opened a channel with another CLN v23.08 peer, using funds from another wallet (
fundchannel_start
,fundchannel_complete
). waited for it to lock in and then tried to splice out 1 sat.This returned a (v2) psbt. I then passed that into
splice_update
. This command didn't return immedidately. After a minute or so I interrupted it.However subsequent calls to either
splice_update
andsplice_signed
(with the signed version) result inCurrently waiting on previous splice command to finish
(code 355,SPLICE_BUSY_ERROR
).How long should I wait? Is there an RPC that tells me what's going on? Should I reboot? :-)
Happy to provide more details, but not sure how to do that without doxxing a bit too much.
The text was updated successfully, but these errors were encountered: