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
If like in ledgerloops/strategy-pit#24 explicit exchange rates are communicated independently from fees, then it might make sense to decouple them from specific loops. After all, if loops partially overlap then they would share the exchange rate and fee for that overlapping piece.
I don't think this would be more efficient though, since nothing is going to move unless there is a loop, so you might as well trace loops first and then do exchange rate negotiation on this much reduced search space of a specific loop, rather than doing it on the entire graph.
Worth considering though, there might be use cases for this approach in highly connected parts of the network. For instance in a "Manhattan mesh" where each node is connected to a north/south/east/west neighbour, there would be many ways to draw a loop but they overlap a lot so there would be only a limited number of exchange rates to propagate.
The text was updated successfully, but these errors were encountered:
If like in ledgerloops/strategy-pit#24 explicit exchange rates are communicated independently from fees, then it might make sense to decouple them from specific loops. After all, if loops partially overlap then they would share the exchange rate and fee for that overlapping piece.
I don't think this would be more efficient though, since nothing is going to move unless there is a loop, so you might as well trace loops first and then do exchange rate negotiation on this much reduced search space of a specific loop, rather than doing it on the entire graph.
Worth considering though, there might be use cases for this approach in highly connected parts of the network. For instance in a "Manhattan mesh" where each node is connected to a north/south/east/west neighbour, there would be many ways to draw a loop but they overlap a lot so there would be only a limited number of exchange rates to propagate.
The text was updated successfully, but these errors were encountered: