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

Relai: Channel looks open but in fact was closed on chain a long ago #436

Open
roeierez opened this issue May 12, 2024 · 4 comments
Open
Assignees
Labels
state::investigating This is currently under investigation

Comments

@roeierez
Copy link
Collaborator

relai issue: https://github.com/breez/breez-sdk-relai/issues/24

Node ID: 03bca8282eb1193b70d50a63e2db922f252cdb2759000376f4de30e5b88f3df24f

Closing tx: https://blockstream.info/tx/e2d38d38b08f13c1cc555c5c898eb12ead3794730b1321ac565609d41575a593
Only the last output (which belongs to the lsp) was swept, the rest are not swept.
This node has a pending payment and the channel returned on listfunds seems opened from the node perspective.

@cdecker
Copy link
Collaborator

cdecker commented May 14, 2024

This node is stuck on the closing transaction. We correctly detect the close, but then cannot use the signer to sign the commitment transaction to get us unstuck.

This could be related to #431. Do we have access to the signer logs? That'd corroborate what we're seeing.

@cdecker cdecker self-assigned this May 14, 2024
@cdecker cdecker added the state::investigating This is currently under investigation label May 14, 2024
@roeierez
Copy link
Collaborator Author

Unfortunately no.

@JordiZDG
Copy link

JordiZDG commented Jun 2, 2024

Any update?

@cdecker
Copy link
Collaborator

cdecker commented Jul 8, 2024

This appears to be an instance of #431. We addressed with a patch added on top of the v24.02gl1 version, cherry-picked from ElementsProject/lightning#7447, and guarded by manual opt-in.

I will use this node to test the patch, since the GL node did not own any funds on this channel, this will test just if we get unstuck correctly. We will then pick a node that had some outputs to sweep and test that separately.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
state::investigating This is currently under investigation
Projects
None yet
Development

No branches or pull requests

3 participants