You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Merging #1247 (6bccdaa) into main (34cdca9) will increase coverage by 0.01%.
The diff coverage is 92.00%.
❗ Current head 6bccdaa differs from pull request most recent head c49c086. Consider uploading reports for the commit c49c086 to get more accurate results
I'm somewhat confused as to the motivation for this PR - ChannelHandshakeConfig is all configuration options which are set at the beginning of a channel and then can not be changed afterwards - its all stuff in the "handshake". Instead, I think we should move things from ChannelConfig which cannot be updated after the handshake, specifically announced_channel (cannot be updated per lightning spec), commit_upfront_shutdown_pubkey (its literally about whether we include the pubkey in the handshake or not).
The reason will be displayed to describe this comment to others. Learn more.
Note that we cannot remove required elements, as old clients will refuse to load data serialized by new clients (which we guarantee won't happen at least across a few releases). We instead need to write the default value with something like (0, Some(DEFAULT_VALUE as u64), option)
I'm somewhat confused as to the motivation for this PR - ChannelHandshakeConfig is all configuration options which are set at the beginning of a channel and then can not be changed afterwards - its all stuff in the "handshake". Instead, I think we should move things from ChannelConfig which cannot be updated after the handshake, specifically announced_channel (cannot be updated per lightning spec), commit_upfront_shutdown_pubkey (its literally about whether we include the pubkey in the handshake or not).
I misunderstood the issue - am I on the right track with #1270? Closing this PR in favor of #1270
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
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.
First step for #216