routing+routerrpc: add multiple outgoing channel restriction #4257
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
joostjager
force-pushed
the
multi-outgoing-chan-restriction
branch
2 times, most recently
from
eb9da33 to
dd4c577
Compare
Roasbeef
requested changes
May 7, 2020
joostjager
force-pushed
the
multi-outgoing-chan-restriction
branch
2 times, most recently
from
077323c to
4744257
Compare
carlaKC
approved these changes
May 11, 2020
joostjager
force-pushed
the
multi-outgoing-chan-restriction
branch
2 times, most recently
from
66ebc1a to
3968af8
Compare
joostjager
force-pushed
the
multi-outgoing-chan-restriction
branch
from
a334cbe to
7660e71
Compare
joostjager
force-pushed
the
multi-outgoing-chan-restriction
branch
from
7660e71 to
25a50b6
Compare
|
Tested channel set restriction with loop out on a dev branch, works. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds the ability to restrict payment pathfinding to a set of outgoing channels. Prior to this, it was only possible to restrict to a single channel.
A use case of channel (set) selection is to not just make the payment, but also obtain the (right) inbound at the same time. This is also a building block that allows loop out channel set selection.