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]: Add the possibility to pay a blinded path when the sender is also the introduction point. #9027

Open
ziggie1984 opened this issue Aug 22, 2024 · 4 comments
Labels
enhancement Improvements to existing features / behaviour

Comments

@ziggie1984
Copy link
Collaborator

I think it makes sense to also allow the introduction point of a blinded path pay the invoice.

@ziggie1984 ziggie1984 added the enhancement Improvements to existing features / behaviour label Aug 22, 2024
@saubyk
Copy link
Collaborator

saubyk commented Aug 28, 2024

It might be a good idea to articulate specific benefits of this scenario, before initiating any dev work here.

If my understanding of route blinding is correct, when the introduction point is also the payer of the invoice then it knows the entire route as well. So there is no privacy benefit for the receiver really.

What possible use cases can benefit from enabling this?

@ellemouton
Copy link
Collaborator

ellemouton commented Aug 28, 2024

If my understanding of route blinding is correct, when the introduction point is also the payer of the invoice then it knows the entire route as well.

No that is incorrect. It just would know the next hop

What possible use cases can benefit from enabling this?

So that a node is able to pay an invoice even if it happens to be the chosen intro node

@carlaKC
Copy link
Collaborator

carlaKC commented Sep 12, 2024

I think it makes sense to also allow the introduction point of a blinded path pay the invoice.

Definitely does! Was excluded from original PRs to keep the scope down.

@AndySchroder
Copy link

Wondering, can the allow-circular-route option allow any hacks to make this work by adding some extra hops in and then routing back through yourself later? For example, it is a hacky way to workaround #7419 (which is a mildly related bug).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Improvements to existing features / behaviour
Projects
None yet
Development

No branches or pull requests

5 participants