Default policies from other lightning nodes #14
Merged
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
dr-orlovsky
requested changes
Dec 31, 2021
grunch
force-pushed
the
issue_12-add-default-policies-from-other-lightning-implementations
branch
2 times, most recently
from
5a31b28
to
5ae5869
Compare
This PR add default policies from the main three implementations Fix LNP-WG#12
grunch
force-pushed
the
issue_12-add-default-policies-from-other-lightning-implementations
branch
from
5ae5869
to
9760b9a
Compare
dr-orlovsky
approved these changes
Jan 6, 2022
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 add default policies from the main three implementations
but is not finished yet, there is no default value for some values
like
feerate_per_kw_rangeon three implementations andmax_htlc_value_in_flight_msat_minon lnd, I wrote this on commentsFix #12