-
Notifications
You must be signed in to change notification settings - Fork 902
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
Channel close prints invalid tx to console #6440
Comments
rustyrussell
added a commit
to rustyrussell/lightning
that referenced
this issue
Jul 31, 2023
We don't actually sign in place, since ->last_tx is assumed unsigned, and I'd have to audit carefully to change that. But we can thread the signed tx through so close's JSON return contains that, rather than the unsigned channel->last_tx. We have to split the "get cmd_id" from "resolve the close commands" though; and of course, as before, we don't actually print the txids of multiple transactions even though we may have multi in flight due to splice! Signed-off-by: Rusty Russell <[email protected]> Changelog-Fixed: JSON-RPC: `close` returns a `tx` field with witness data populated (i.e. signed). Fixes: ElementsProject#6440
rustyrussell
added a commit
to rustyrussell/lightning
that referenced
this issue
Jul 31, 2023
Thread the signed tx through so close's JSON return contains that, rather than the unsigned channel->last_tx. We have to split the "get cmd_id" from "resolve the close commands" though; and of course, as before, we don't actually print the txids of multiple transactions even though we may have multi in flight due to splice! Signed-off-by: Rusty Russell <[email protected]> Changelog-Fixed: JSON-RPC: `close` returns a `tx` field with witness data populated (i.e. signed). Fixes: ElementsProject#6440
rustyrussell
added a commit
to rustyrussell/lightning
that referenced
this issue
Jul 31, 2023
Thread the signed tx through so close's JSON return contains that, rather than the unsigned channel->last_tx. We have to split the "get cmd_id" from "resolve the close commands" though; and of course, as before, we don't actually print the txids of multiple transactions even though we may have multi in flight due to splice! Signed-off-by: Rusty Russell <[email protected]> Changelog-Fixed: JSON-RPC: `close` returns a `tx` field with witness data populated (i.e. signed). Fixes: ElementsProject#6440
rustyrussell
added a commit
to rustyrussell/lightning
that referenced
this issue
Jul 31, 2023
Thread the signed tx through so close's JSON return contains that, rather than the unsigned channel->last_tx. We have to split the "get cmd_id" from "resolve the close commands" though; and of course, as before, we don't actually print the txids of multiple transactions even though we may have multi in flight due to splice! Signed-off-by: Rusty Russell <[email protected]> Changelog-Fixed: JSON-RPC: `close` returns a `tx` field with witness data populated (i.e. signed). Fixes: ElementsProject#6440
litch
pushed a commit
to litch/lightning
that referenced
this issue
Aug 11, 2023
Thread the signed tx through so close's JSON return contains that, rather than the unsigned channel->last_tx. We have to split the "get cmd_id" from "resolve the close commands" though; and of course, as before, we don't actually print the txids of multiple transactions even though we may have multi in flight due to splice! Signed-off-by: Rusty Russell <[email protected]> Changelog-Fixed: JSON-RPC: `close` returns a `tx` field with witness data populated (i.e. signed). Fixes: ElementsProject#6440
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Blockstream Store
lightning-cli close 712394x2573x1 1
prints this to console:The complete tx is transmitted but invalid tx where the witness is missing is printed to console.
The text was updated successfully, but these errors were encountered: