-
Notifications
You must be signed in to change notification settings - Fork 411
Channel Establishment for V3 Channels #3792
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
Channel Establishment for V3 Channels #3792
Conversation
👋 I see @wpaulino was un-assigned. |
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.
Cool, basically all LGTM.
@@ -16153,22 +16154,28 @@ mod tests { | |||
} | |||
|
|||
#[test] | |||
fn test_anchors_zero_fee_htlc_tx_fallback() { | |||
fn test_anchors_zero_fee_htlc_tx_downgrade() { |
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.
Congrats, you touched it, now you get to move it out of channelmanager
into some other test-specific file that isn't 15000 lines of code 😂
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.
Done this in a follow up in #3797 so that move + format can be reviewed separately.
lightning/src/util/config.rs
Outdated
/// back to a `anchors_zero_fee_htlc` (if [`Self::negotiate_anchors_zero_fee_htlc_tx`] | ||
/// is set) or `static_remote_key` channel. | ||
/// | ||
/// *Implies [`Self::negotiate_anchors_zero_fee_htlc_tx`].* |
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.
These are in conflict - one says we'll fall back if its set, the other says that its implied (ie always set) if we set this flag.
👋 The first review has been submitted! Do you think this PR is ready for a second reviewer? If so, click here to assign a second reviewer. |
✅ Added second reviewer: @valentinewallace |
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.
LGTM after Matt's comments are addressed
3a36506
to
b9ec89c
Compare
Removed conflicting docs statement + opened followup for test separation (felt wrong to do move+format in the same PR, happy to include if we want it in here). |
🔔 1st Reminder Hey @TheBlueMatt @wpaulino! This PR has been waiting for your review. |
1 similar comment
🔔 1st Reminder Hey @TheBlueMatt @wpaulino! This PR has been waiting for your review. |
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.
Sorry for the delay, here's a first pass :)
🔔 2nd Reminder Hey @TheBlueMatt @wpaulino! This PR has been waiting for your review. |
1 similar comment
🔔 2nd Reminder Hey @TheBlueMatt @wpaulino! This PR has been waiting for your review. |
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.
Another pass :)
b9ec89c
to
892d87a
Compare
Major change in push is using get_initial_channel_type in channel type downgrades to DRY up the code a bit. |
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.
Thank you for the downgrade tests ! Just three nits at this point :)
892d87a
to
e56e32a
Compare
🔔 3rd Reminder Hey @TheBlueMatt @wpaulino! This PR has been waiting for your review. |
1 similar comment
🔔 3rd Reminder Hey @TheBlueMatt @wpaulino! This PR has been waiting for your review. |
🔔 4th Reminder Hey @TheBlueMatt @wpaulino! This PR has been waiting for your review. |
Rebased + added additional comment on assert - diff. |
Two followups for this to do some test cleaning while we're here:
|
Useful for the commits that follow where we add more downgrade tests.
e430212
to
99c645e
Compare
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #3792 +/- ##
==========================================
+ Coverage 89.91% 89.93% +0.02%
==========================================
Files 160 160
Lines 129307 129579 +272
Branches 129307 129579 +272
==========================================
+ Hits 116262 116539 +277
+ Misses 10355 10352 -3
+ Partials 2690 2688 -2 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
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.
Grrr, one issue sorry.
lightning/src/ln/channel.rs
Outdated
eligible_features.clear_anchor_zero_fee_commitments(); | ||
eligible_features.clear_anchors_zero_fee_htlc_tx(); | ||
assert!(!eligible_features.supports_anchor_zero_fee_commitments()); | ||
assert!(!eligible_features.supports_anchors_nonzero_fee_htlc_tx()); |
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.
Isn't this trivially reachable if a peer sets the nonzero-fee-htlc-tx feature bit? Generally, though, all the assertions here seem like they could be debug_assertions or elided entirely (asserting that we don't support something we just cleared probably belongs in a features test, and I believe already exists).
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.
Will remove the feature bit asserts 👍
Isn't this trivially reachable if a peer sets the nonzero-fee-htlc-tx feature bit?
ofc, it should be on channel_type
🤦♀️
Rather than duplicating our channel type preference ordering in downgrade logic, make a modified version of the remote peer's supported features and remove our current channel type from it to get the next preferred channel type.
To allow testing along the way in this PR, turn on negotiation of zero fee channels. Co-authored-by: Matt Corallo <[email protected]>
Sender: MUST set `feerate_per_kw` to zero Receiver: MUST fail the channel if `feerate_per_kw` != 0 Co-authored-by: Matt Corallo <[email protected]>
Like anchor channels, these channels require that the user reserves a UTXO to bump the channel. If we automatically accept this channel type and the user does not have such reserve available, they are at risk of losing funds because they cannot fee bump the channel.
99c645e
to
23de01c
Compare
// We should never have negotiated `anchors_nonzero_fee_htlc_tx` because it can result in a | ||
// loss of funds. | ||
let channel_type = &funding.channel_transaction_parameters.channel_type_features; | ||
assert!(!channel_type.supports_anchors_nonzero_fee_htlc_tx()); |
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.
Moved this assert up because we should never negotiate a non-zero-htlc-anchor channel, and it's a risk of lost funds if we do.
Couldn't see a historical reason why we only checked it if the channel type was supports_anchors_zero_fee_htlc_tx
- went back a few commits and couldn't find reasoning. cc @TheBlueMatt
Removed asserts + moved |
This PR updates the channel establishment flow to allow and validate V3 channels (behind
test
flag).