Skip to content
This repository has been archived by the owner on Jan 10, 2025. It is now read-only.

LSPS2: Mitigation against prepayment probing. #46

Conversation

ZmnSCPxj-jr
Copy link
Contributor

@ZmnSCPxj-jr ZmnSCPxj-jr commented Aug 7, 2023

Fixes: #44

This is just one of two pull requests for this. Please wait for the other one as well. #47 is the other one.

In this particular pull request, we assume that the conditional probability of an actual payment occurring after a prepayment probe reaches the client is very high, and that any deviation from 100% can be considered an operational overhead of the LSP. This also only applies in "LSP trusts client" model; if the model is "client trusts LSP" then the LSP can defer broadcasting the funding transaction and if the payment does not push through (i.e. prepayment probe occurred but no payment) then the LSP simply does not broadcast the signed funding transaction but instead simply reuses the same inputs for a different, paying service.

@SeverinAlexB
Copy link
Collaborator

Can we close this or is this still a concern?

@ZmnSCPxj-jr
Copy link
Contributor Author

Dunno if still a concern. shrug

@ZmnSCPxj-jr ZmnSCPxj-jr closed this May 4, 2024
@ZmnSCPxj-jr ZmnSCPxj-jr deleted the lsps2-mitigation branch August 22, 2024 15:00
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Prepayment probing conflicts with LSPS2 (and JIT Channels in general)
2 participants