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

LSPS2: Forward intercepted htlc failure cases #42

Open
johncantrell97 opened this issue Nov 15, 2023 · 0 comments
Open

LSPS2: Forward intercepted htlc failure cases #42

johncantrell97 opened this issue Nov 15, 2023 · 0 comments

Comments

@johncantrell97
Copy link
Contributor

Once we receive ChannelReady event from LDK we iterate over all of the intercepted HTLCs we are holding, remove the fee, and then attempt to forward each one individually.

It's possible for forwards to fail but we will not receive any kind of signal that this happened. As an LSP we would want to know how much fee is still owed for the channel we just opened. We could then continue to take fee from future HTLCs until we have collected what we were owed.

We might also want to close the channel should the opening payment fail for whatever reason.

@tnull was going to look into how this could work with LDK as it doesn't appear to be possible to extract this information from LDK as it stands. We might be able to use HTLCHandlingFailed event in combination with next hop and payment_hash information. This still wouldn't help us identify which parts of a MPP failed, we would need a way to tie the InterceptId to the failed HTLC event.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant