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
Switch to a max counterparty's
dust_limit_satoshis
constant #845Switch to a max counterparty's
dust_limit_satoshis
constant #845Changes from 2 commits
16619ff
ce56e3f
b307c1f
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
Large diffs are not rendered by default.
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.
Since we select the
holder_selected_channel_reserve_satoshis
, could we just ensure that we never select a reserve belowMIN_DUST_LIMIT_SATOSHIS
?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.
Do you mean instead of returning an API error, rouding up the
channel_reserve_satoshis
with MIN_DUST_LIMIT_SATOSHIS.I think I prefer the user to swallow the error and having manually to bounce up the channel value instead of us doing it automatically. We might silently encroach on its expected liquidity ready to use and falsify higher application logic like an accounting app... Though not a strong opinion here.
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 just seem like it doesn't make sense for
get_holder_selected_channel_reserve_satoshis
to ever return a value less than330
. But, fine to leave that for follow-upThere 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.
I don't think our API prevent a user to try a
new_outbound
with less than 330 sat ? And if does soget_holder_selected_channel_reserve_satoshis
will return the exact value.That said there is a TODO to make more sense of
get_holder_selected_channel_reserve_satoshis
. We can address it at that time.