-
Notifications
You must be signed in to change notification settings - Fork 470
Expose channel reserve in open channel requests #4731
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
Open
DeepCogNeural
wants to merge
2
commits into
lightningdevkit:main
Choose a base branch
from
DeepCogNeural:codex/expose-open-channel-reserve
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+115
−9
Open
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,11 @@ | ||
| # API Updates | ||
|
|
||
| * `Event::OpenChannelRequest::params` now exposes the channel reserve in | ||
| `msgs::ChannelParameters::channel_reserve_satoshis`. For V1 channels this is | ||
| the reserve provided in `open_channel`; for V2 channels this is derived from | ||
| the initiator's funding contribution, the V2 reserve rules, and | ||
| `disable_channel_reserve`. For V2 channels the finally enforced reserve may | ||
| be higher if the acceptor later contributes additional funds. | ||
| `msgs::CommonOpenChannelFields::channel_parameters` is now crate-internal | ||
| because common open-channel fields alone do not contain enough information to | ||
| construct the full `ChannelParameters`. |
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.
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.
For V2 dual-funded channels the reserve is computed from only the peer's
funding_satoshis, but the reserve actually enforced on the holder is derived at accept time from the total channel value (our_funding_contribution + msg.funding_satoshis, seeInboundV2Channel::new). If the acceptor contributes funds (as is the whole point of dual funding), the value exposed here will be lower than the reserve that ultimately applies. At event time the acceptor's contribution isn't known yet, so this can't be fully accurate — but worth documenting on the field/changelog that for V2 this reflects only the initiator's contribution, otherwise consumers may rely on a value that doesn't match the final reserve.