lnpeer: send channel_update on channel_reestablish#10635
Merged
Conversation
If we have forwarding enabled, send a channel_update message to the peer after a channel_reestablish. The peer needs to know our channel constraints to receive a payment (for r_tags or blinded path) and sending it just once on mark_open might not be enough as the peer could miss it, lose it or it might get out of date if we'd change our forwarding fees. See spesmilo#10630 (comment).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
If we have forwarding enabled, send a channel_update message to the peer after a channel_reestablish.
The peer needs to know our channel constraints to receive a payment (e.g. for r_tags or blinded paths) and sending it just once on mark_open might not be enough as the peer could miss it, lose it or it might get out of date if we'd change our forwarding fees. See #10630 (comment).