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.
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
Peer inbound weighted average fee strategy + Local balance proportional max_htlc_msat rule #104
base: master
Are you sure you want to change the base?
Peer inbound weighted average fee strategy + Local balance proportional max_htlc_msat rule #104
Changes from 10 commits
0ad2de3
91f2998
06982ad
595315b
97a705f
e67f771
e8679d2
da53ce5
c242987
e7dfd08
8510607
001f620
eade0e8
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's probably best to have a hardcoded upper limit for
num_slices
here, so we don't spam the network (e.g. 10)There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
alternatively, we could define a 'minimum slice size', so that large channels can use more slices than small channels (e.g. 200_000)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For choosing the number of slices for large channels, would the system automatically choose from multiple policies if we set a
chan.min_capacity
etc. and so we could define different slice counts for different sizes?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Well I was thinking along the lines of
so the number of slices is capped at 10 for small channels, or higher if the channel capacity allows for more.