-
Notifications
You must be signed in to change notification settings - Fork 0
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
Routing Considerations #2
Comments
I want to make sure i understand our goal by putting it into my own words. We want to maximize
and we want to minimize
Here is a paste from the notes I took from when we met up. Add channels to be a cut node. (Or join pendants to the graph so there is a flow.) |
Everything you said is correct. To explain the last two on your notes:
There is a vulnerability in the LN routing algorithm which allows the balance of a channel to be guessed by essentially brute forcing payments of increasing amount until the node forwards the payment. It can be done for free and takes up to a min per channel balance revealed.
An alternative routing algorithm to increase the number of hops for privacy but still pay the cheapest fee. |
We want to fold the network in on itself. Picking nodes at random and finding the shortest paths between them will help us identify the center of the network. From there, we can do a breadth first search to find the edge of the network. These are the nodes that we want to find the longest shortest paths between. I want to experiment by shortening the shortest paths between 4 mutually distant edge nodes. |
A routing node seeking profit should:
Costs need to be reduced:
A node should find the optimal channel placement and fee rate. Placing a channel should either increase routed payments or decrease rebalancing costs.
A node can only view the channel capacity of other nodes. It cannot see the balances.
The text was updated successfully, but these errors were encountered: