-
Notifications
You must be signed in to change notification settings - Fork 377
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
Require inbound channels with anchor outputs to be accepted manually #2368
Require inbound channels with anchor outputs to be accepted manually #2368
Conversation
2329307
to
ed14d0e
Compare
Now that all of the core functionality for anchor outputs has landed, we're ready to remove the config flag that was temporarily hiding it from our API.
ed14d0e
to
dece81e
Compare
Since the use of channels with anchor outputs requires a reserve of onchain funds to handle channel force closures, it would be irresponsible to allow a node to accept inbound channel without first consulting such reserves. To allow users to do so, we require such channels be manually accepted.
dece81e
to
e6348b8
Compare
Codecov ReportPatch coverage:
❗ Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more. Additional details and impacted files@@ Coverage Diff @@
## main #2368 +/- ##
==========================================
+ Coverage 90.30% 90.31% +0.01%
==========================================
Files 106 106
Lines 54900 54948 +48
Branches 54900 54948 +48
==========================================
+ Hits 49576 49628 +52
+ Misses 5324 5320 -4
☔ View full report in Codecov by Sentry. |
The merge-base changed after approval.
@@ -1100,6 +1100,15 @@ pub fn create_chan_between_nodes_with_value_init<'a, 'b, 'c>(node_a: &Node<'a, ' | |||
assert_eq!(open_channel_msg.temporary_channel_id, create_chan_id); | |||
assert_eq!(node_a.node.list_channels().iter().find(|channel| channel.channel_id == create_chan_id).unwrap().user_channel_id, 42); | |||
node_b.node.handle_open_channel(&node_a.node.get_our_node_id(), &open_channel_msg); | |||
if node_b.node.get_current_default_configuration().manually_accept_inbound_channels { |
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.
Thanks, I was going to need this anyway for V2 establishment :)
#[test] | ||
fn test_inbound_anchors_manual_acceptance() { | ||
// Tests that we properly limit inbound channels when we have the manual-channel-acceptance | ||
// flag set and (sometimes) accept channels as 0conf. |
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.
What conditions correspond with “sometimes” here?
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.
Ah, I copied another test as a template but forgot to update the comment here. Will fix in a future PR.
The merge-base changed after approval.
Oh joy github is broken. |
Since the use of channels with anchor outputs requires a reserve of onchain funds to handle channel force closures, it would be irresponsible to allow a node to accept inbound channel without first consulting such reserves. To allow users to do so, we require such channels be manually accepted.
Depends on #2361 and #2367.