-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Better privacy for sender when making LN payments #2530
Comments
Taking this one |
I can't think of a straightforward way to solve this problem. The use case described in the issue needs a way to use the The My suggestion is that when the I think this would work and has a worst-case complexity of Related: |
Since we don't allow cycles, I think the above is NP-Complete. The use case described in the issue really just needs hops != 1 so we can just find two paths using Yen's |
Since If a user has a channel with the target, this could also be solved by having an outgoing channel restriction that is not with the target, but this requires knowing that one has a channel with the target and then choosing an outgoing channel. In cases where the user doesn't know that they have a channel with the target or if they do, don't want to perform more mental work (i.e. choosing an outgoing chan), then adding an |
Thank you Crypt-IQ, I also think --indirect would suffice. |
Closing this issue as the problem is better posed to and addressed at the spec level, rather than coming up with implementation level "hack" |
Privacy problem
I have only private channels from my node and one of them is with Merchant (autopilot did it, not my fault). I pay an invoice from my node to Merchant and Merchant can see that it comes from the private channel I have with them. As the merchant did not include this private channel in the bolt11 as a route hint they can be pretty sure that it was my node who is the one who paid and that it was not a payment I relayed for someone else.
Solution
Make sure that the payment is relayed through at least X hops before it reaches its destination.
Solution today
This can be solved today by taking the node id and amount from the bolt 11 invoice, send it to queryroutes, removing any routes with not enough hops and then pay it with sendtoroute.
Proposed future solution
An easier solution for the user would be to add an option to sendpayment to specify minimum amount of hops. For example "--min_hops 3"
The text was updated successfully, but these errors were encountered: