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]: MPP compatibility for single hop blinded paths #9332

Open
ziggie1984 opened this issue Dec 4, 2024 · 1 comment
Open

[feature]: MPP compatibility for single hop blinded paths #9332

ziggie1984 opened this issue Dec 4, 2024 · 1 comment
Labels
blinded paths enhancement Improvements to existing features / behaviour mission control

Comments

@ziggie1984
Copy link
Collaborator

Right now when we send to a blinded route with only 1 hop after the intropoint we immediatly fail the payment and won't retry. The main reason for this was that we did not want to penalize the introduction node pair to the final hop because it could be gamed potentially.

However I think in combination of making the MC data for blinded paths volatile (not persisting the data) we can also get rid of this check as well:

// Note that if LND is extended to support multiple blinded
// routes, this will terminate the payment without re-trying
// the other routes.
if introIdx == len(route.hops.Val)-1 {
i.finalFailureReason = &reasonError

@ziggie1984 ziggie1984 added enhancement Improvements to existing features / behaviour mission control blinded paths labels Dec 4, 2024
@ziggie1984
Copy link
Collaborator Author

Should be done after #9321

@ziggie1984 ziggie1984 changed the title [feature]: MPP compatibility for single hop blined paths [feature]: MPP compatibility for single hop blinded paths Dec 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
blinded paths enhancement Improvements to existing features / behaviour mission control
Projects
None yet
Development

No branches or pull requests

1 participant