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: fix update_fee cap. #7068

Merged
merged 2 commits into from Feb 13, 2024

Conversation

rustyrussell
Copy link
Contributor

We would sometimes propose fees which we couldn't afford, and thus the peer would get upset: if we didn't recover it could cause force closes.

This was because we didn't take into account that pending htlcs will remove our total available funds.

Changelog-Fixes: Protocol: Don't upset peers by sending update_fee with fees we cannot afford in the case where HTLCs are large.

We would sometimes propose fees which we couldn't afford, and thus the
peer would get upset: if we didn't recover it could cause force closes.

This was because we didn't take into account that pending htlcs will
remove our total available funds.

Changelog-Fixes: Protocol: Don't upset peers by sending `update_fee` with fees we cannot afford in the case where HTLCs are large.
@rustyrussell rustyrussell added the protocol These issues are protocol level issues that should be discussed on the protocol spec repo label Feb 13, 2024
@rustyrussell rustyrussell added this to the v24.02 milestone Feb 13, 2024
@cdecker cdecker merged commit abfe55e into ElementsProject:master Feb 13, 2024
36 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
protocol These issues are protocol level issues that should be discussed on the protocol spec repo
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants