Expose channel_reserve_satoshis via ChannelParameters
#4319
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.
Summary
channel_reserve_satoshis: Option<u64>field toChannelParametersstructSome(value)with the explicit reserve fromopen_channelmessageNonesince reserve is calculated from total channel value (initiator + acceptor funding), which isn't known atOpenChannelRequesttimechannel_parameters()fromCommonOpenChannelFieldsto individualOpenChannelandOpenChannelV2impls to handle V1/V2 difference correctlytest_open_channel_request_channel_reserve_satoshisto verify the implementationFixes #3909
Revives the closed PR #3910 with the approach suggested by reviewers:
Option<u64>instead of trying to read from wire for V2 (which doesn't have this field)channel_parameters()toOpenChannel/OpenChannelV2Test plan
cargo check -p lightningpassescargo test -p lightning --lib)test_open_channel_request_channel_reserve_satoshisvalidates V1 channels correctly populate the fieldchannel_open_testspass🤖 Generated with Claude Code