You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
in getting started we write:
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
The text was updated successfully, but these errors were encountered: