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

[feature]: granular decrease in added feerate security buffer #9124

Open
JssDWt opened this issue Sep 19, 2024 · 1 comment
Open

[feature]: granular decrease in added feerate security buffer #9124

JssDWt opened this issue Sep 19, 2024 · 1 comment
Labels
enhancement Improvements to existing features / behaviour

Comments

@JssDWt
Copy link
Contributor

JssDWt commented Sep 19, 2024

Is your feature request related to a problem? Please describe.
In #8096 a fee buffer was added for routing htlcs. The buffer contains 2x the current chain fee rate + 1 additional htlc. In very high-fee scenarios the 2x fee buffer causes small channels to be unable to forward any htlcs. In very high fee scenarios adding 2x the chain fee rate is a much larger increase than in low-fee scenarios, effectively jamming channels entirely.

Describe the solution you'd like
Add a granular decrease in the added buffer based on the current chain fee estimate. CLN has implemented this granular decrease already in ElementsProject/lightning#7063, with accompanying issue ElementsProject/lightning#6974. See theory there.

Here's the expected curve for the added buffer fee rate.
image

@JssDWt JssDWt added the enhancement Improvements to existing features / behaviour label Sep 19, 2024
@ziggie1984
Copy link
Collaborator

I think that makes sense thank you for the idea!

As long as the the fee is calculated percentage wise, you can limit the feeBuffer by limiting the ; max-commit-fee-rate-anchors setting.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Improvements to existing features / behaviour
Projects
None yet
Development

No branches or pull requests

2 participants