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

channeld: don't send multiple update_fee until previous settled. #3325

Closed
wants to merge 1 commit into from

Conversation

rustyrussell
Copy link
Contributor

Our feerate logic is overly simplistic (ha!) and we seem to get confused
on back-to-back feerate updates. Fixing it seems to require much more
complex feerate logic which I am deeply reluctant to implement, as it's
terribly fragile and will be discarded eventually once we have
simplified commitments.

Fixes: #2661
Signed-off-by: Rusty Russell [email protected]
Changelog-Fixed: Occasional 'Bad commit_sig signature' channel failures with fee updates (#2661)

@rustyrussell rustyrussell added this to the 0.7.4 milestone Dec 9, 2019
Our feerate logic is overly simplistic (ha!) and we seem to get confused
on back-to-back feerate updates.  Fixing it seems to require much more
complex feerate logic which I am deeply reluctant to implement, as it's
terribly fragile and will be discarded eventually once we have
simplified commitments.

Fixes: ElementsProject#2661
Signed-off-by: Rusty Russell <[email protected]>
Changelog-Fixed: Occasional 'Bad commit_sig signature' channel failures with fee updates (ElementsProject#2661)
@rustyrussell
Copy link
Contributor Author

This doesn't work.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Invalid signature on reconnection eclair/c-lightning
1 participant