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

Configurable anchor output max commitment feerate #1718

Merged
merged 3 commits into from
Mar 8, 2021

Conversation

t-bast
Copy link
Member

@t-bast t-bast commented Mar 4, 2021

It makes sense to allow node operators to configure the value they want to use as a maximum threshold for anchor outputs commitment tx feerate.

This allows node operators to raise this value when mempools start getting full in anticipation of a potential rise of the min-relay-fee.

This value can also be overridden for specific nodes.

It makes sense to allow node operators to configure the value they want
to use as a maximum threshold for anchor outputs commitment tx feerate.

This allows node operators to raise this value when mempools start getting
full in anticipation of a potential rise of the min-relay-fee.

This value can also be overridden for specific nodes.
@t-bast t-bast requested a review from pm47 March 4, 2021 17:53
pm47
pm47 previously approved these changes Mar 8, 2021
@t-bast t-bast merged commit 92e53dc into master Mar 8, 2021
@t-bast t-bast deleted the configurable-anchor-max-feerate branch March 8, 2021 15:03
tompro pushed a commit to tompro/eclair that referenced this pull request Mar 21, 2021
It makes sense to allow node operators to configure the value they want
to use as a maximum threshold for anchor outputs commitment tx feerate.

This allows node operators to raise this value when mempools start getting
full in anticipation of a potential rise of the min-relay-fee.

This value can also be overridden for specific nodes.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants