-
Notifications
You must be signed in to change notification settings - Fork 901
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
lightning-rf #740 set feespike factor to 2 #3589
lightning-rf #740 set feespike factor to 2 #3589
Conversation
0b47e45
to
78335ef
Compare
Surprise, we have hardcoded values in tests... I wanted to remove them ever since I got started with the elements support, since they can break way too easily. |
ee60bd1
to
3effa3c
Compare
e1efcef
to
2c7f8b4
Compare
Changelog-Fixed: Use lightning-rfc ElementsProject#740 feespike margin factor of 2
2c7f8b4
to
9f0064c
Compare
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.
* non-funder can't add any non-dust HTLCs (since the funder would | ||
* have to pay the additional fee, but it can't afford to). This | ||
* leads to the channel starving at the feast! This was reported by | ||
* ACINQ's @t-bast | ||
* (https://github.com/lightningnetwork/lightning-rfc/issues/728) and | ||
* demonstrated with c-lightning by @m-schmook | ||
* demonstrated with c-lightning by @m-schmoock |
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.
Sorry about mistyping your nickname btw 😉
This PR makes our channel lockup drain mitigation 86c28b2 compatible with the upcoming changes of the lightning/bolts#740 wich will set this value to a factor of
2
.