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

[feature] Allow the recovering of (outgoing) HTLCs in a DLP case. #1137

Closed
ziggie1984 opened this issue Feb 11, 2024 · 3 comments
Closed

[feature] Allow the recovering of (outgoing) HTLCs in a DLP case. #1137

ziggie1984 opened this issue Feb 11, 2024 · 3 comments

Comments

@ziggie1984
Copy link
Contributor

ziggie1984 commented Feb 11, 2024

Currently when having a data loss we are still able to recover our amount of funds from the remote commitment transaction using the DLP protocol. However when there are outgoing HTLCs on the Commitment we are currently not able to recover those although it would be easily possible if the remote peer would provide us data so that we would reconstruct the witnessScript of the ougoing HTLC output on the remote commitment transaction.

Maybe we could just add additional data to the channel_reestablish msg:

HTLC:

Needed to reconstruct the witness script of the HTLC on the remote commitment:

  • Hash
  • Absolute Timelock of the HTLC (could be grinded but why not provided it when we are at it?)
  • CommitmentPoint (already provided in the channel_reestablish msg.
@TheBlueMatt
Copy link
Collaborator

Most nodes are moving to do this via peer backups instead.

@t-bast
Copy link
Collaborator

t-bast commented Feb 13, 2024

Yes, encrypted peer backups are way superior because you can fully resume a channel without even needing to close it. This has been used in production for almost 3 years for Phoenix, I highly recommend implementing this!

@ziggie1984
Copy link
Contributor Author

Sounds good, closing in favour of #1110

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

3 participants