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

#PickhardtPayments: fast mode: prune distant edges from graph #19

Open
C-Otto opened this issue May 8, 2022 · 1 comment
Open

#PickhardtPayments: fast mode: prune distant edges from graph #19

C-Otto opened this issue May 8, 2022 · 1 comment
Labels
enhancement New feature or request

Comments

@C-Otto
Copy link
Owner

C-Otto commented May 8, 2022

Is your feature request related to a problem? Please describe.
For any payment between nodes A and B the lightning network might contain channels that are very distant from both A and B. Considering those for the MPP computation seems less beneficial compared to "closer" edges.

Describe the solution you'd like
Add a "fast mode" that prunes such edges from the graph to speed up the computation. This should be optional.

@C-Otto C-Otto added the enhancement New feature or request label May 8, 2022
@C-Otto C-Otto changed the title Feature Request: Pickhardt Payments: fast mode: prune distant edges from graph Feature Request: #PickhardtPayments: fast mode: prune distant edges from graph May 8, 2022
@C-Otto C-Otto changed the title Feature Request: #PickhardtPayments: fast mode: prune distant edges from graph #PickhardtPayments: fast mode: prune distant edges from graph May 8, 2022
@renepickhardt
Copy link
Contributor

may be relevant: renepickhardt/mpp-splitter#13 I am currently considering to basically multiply the cost of an edge with a number that increases exponentially with the topological distance of the edge from sender and recipient pair before pruning

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants