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

Problem with automatically connecting to hub nodes #138

Closed
renepickhardt opened this issue Feb 8, 2020 · 0 comments
Closed

Problem with automatically connecting to hub nodes #138

renepickhardt opened this issue Feb 8, 2020 · 0 comments

Comments

@renepickhardt
Copy link
Contributor

in getting started we write:

While this trade-off simplifies the user interface and user experience, it introduces a Single Point of Failure (SPoF) and a potential privacy compromise, as these "hub nodes" become indispensable and can see all the user's transactions.

they can see all payments of a user but not to whom those payments go. unless of course the destination is also using such a hub...

The situation might be a little different in the Phoenix case where route computation is also deligated to the ACINQ server. While they promise that with trampoline this can be outsourced to any set of trampoline nodes this is still tricky

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

1 participant