-
Notifications
You must be signed in to change notification settings - Fork 403
LSPS2: Fail intercepted htlcs if lsp open channel fails for whatever reason #3479
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
Labels
Comments
This was referenced May 17, 2024
martinsaposnic
added a commit
to martinsaposnic/rust-lightning
that referenced
this issue
Apr 7, 2025
Add two LSPS2Service methods: 'Abandoned' prunes all channel open state. 'Failed' resets JIT channel to fail HTLCs. It allows a retry on channel open. Closes lightningdevkit#3479.
martinsaposnic
added a commit
to martinsaposnic/rust-lightning
that referenced
this issue
Apr 7, 2025
Add two LSPS2Service methods: 'Abandoned' prunes all channel open state. 'Failed' resets JIT channel to fail HTLCs. It allows a retry on channel open. Closes lightningdevkit#3479.
martinsaposnic
added a commit
to martinsaposnic/rust-lightning
that referenced
this issue
Apr 20, 2025
Add two LSPS2Service methods: 'Abandoned' prunes all channel open state. 'Failed' resets JIT channel to fail HTLCs. It allows a retry on channel open. Closes lightningdevkit#3479.
martinsaposnic
added a commit
to martinsaposnic/rust-lightning
that referenced
this issue
May 3, 2025
Add two LSPS2Service methods: 'Abandoned' prunes all channel open state. 'Failed' resets JIT channel to fail HTLCs. It allows a retry on channel open. Closes lightningdevkit#3479.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
There's a scenario where we emit
OpenChannel
event to the LSP to handle. From thereliquidity
is waiting for them to feed us aChannelReady
event but if they refuse or fail to open the channel then this HTLC is just stuck forever.We should expose a method the LSP can use to tell us to go ahead and fail all the pending payments backwards.
The text was updated successfully, but these errors were encountered: