Skip to content

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

Merged
merged 8 commits into from
Jun 6, 2025

Conversation

carlaKC
Copy link
Contributor

@carlaKC carlaKC commented May 22, 2025

This PR updates the channel establishment flow to allow and validate V3 channels (behind test flag).

@ldk-reviews-bot
Copy link

ldk-reviews-bot commented May 22, 2025

👋 I see @wpaulino was un-assigned.
If you'd like another reviewer assignemnt, please click here.

@carlaKC carlaKC requested a review from TheBlueMatt May 22, 2025 15:43
@carlaKC carlaKC mentioned this pull request May 22, 2025
36 tasks
Copy link
Collaborator

@TheBlueMatt TheBlueMatt left a 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() {
Copy link
Collaborator

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 😂

Copy link
Contributor Author

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.

Comment on lines 209 to 212
/// 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`].*
Copy link
Collaborator

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.

@ldk-reviews-bot
Copy link

👋 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.

@ldk-reviews-bot
Copy link

✅ Added second reviewer: @valentinewallace

@wpaulino wpaulino requested review from wpaulino and removed request for valentinewallace May 22, 2025 18:17
Copy link
Contributor

@wpaulino wpaulino left a 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

@carlaKC
Copy link
Contributor Author

carlaKC commented May 23, 2025

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).

@carlaKC carlaKC requested review from wpaulino and TheBlueMatt May 23, 2025 20:54
@ldk-reviews-bot
Copy link

🔔 1st Reminder

Hey @TheBlueMatt @wpaulino! This PR has been waiting for your review.
Please take a look when you have a chance. If you're unable to review, please let us know so we can find another reviewer.

1 similar comment
@ldk-reviews-bot
Copy link

🔔 1st Reminder

Hey @TheBlueMatt @wpaulino! This PR has been waiting for your review.
Please take a look when you have a chance. If you're unable to review, please let us know so we can find another reviewer.

Copy link
Contributor

@tankyleo tankyleo left a 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 :)

@ldk-reviews-bot
Copy link

🔔 2nd Reminder

Hey @TheBlueMatt @wpaulino! This PR has been waiting for your review.
Please take a look when you have a chance. If you're unable to review, please let us know so we can find another reviewer.

1 similar comment
@ldk-reviews-bot
Copy link

🔔 2nd Reminder

Hey @TheBlueMatt @wpaulino! This PR has been waiting for your review.
Please take a look when you have a chance. If you're unable to review, please let us know so we can find another reviewer.

Copy link
Contributor

@tankyleo tankyleo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Another pass :)

@carlaKC carlaKC force-pushed the 3789-channelestablishment branch from b9ec89c to 892d87a Compare May 29, 2025 15:50
@carlaKC
Copy link
Contributor Author

carlaKC commented May 29, 2025

Major change in push is using get_initial_channel_type in channel type downgrades to DRY up the code a bit.
Otherwise addressed nits + added some tests in fixups (full diff).

@carlaKC carlaKC requested a review from tankyleo May 29, 2025 15:53
Copy link
Contributor

@tankyleo tankyleo left a 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 :)

@carlaKC carlaKC force-pushed the 3789-channelestablishment branch from 892d87a to e56e32a Compare May 30, 2025 20:23
@carlaKC
Copy link
Contributor Author

carlaKC commented May 30, 2025

@ldk-reviews-bot
Copy link

🔔 3rd Reminder

Hey @TheBlueMatt @wpaulino! This PR has been waiting for your review.
Please take a look when you have a chance. If you're unable to review, please let us know so we can find another reviewer.

1 similar comment
@ldk-reviews-bot
Copy link

🔔 3rd Reminder

Hey @TheBlueMatt @wpaulino! This PR has been waiting for your review.
Please take a look when you have a chance. If you're unable to review, please let us know so we can find another reviewer.

@ldk-reviews-bot
Copy link

🔔 4th Reminder

Hey @TheBlueMatt @wpaulino! This PR has been waiting for your review.
Please take a look when you have a chance. If you're unable to review, please let us know so we can find another reviewer.

@carlaKC
Copy link
Contributor Author

carlaKC commented Jun 4, 2025

Rebased + added additional comment on assert - diff.

@carlaKC
Copy link
Contributor Author

carlaKC commented Jun 4, 2025

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.
@carlaKC carlaKC force-pushed the 3789-channelestablishment branch 2 times, most recently from e430212 to 99c645e Compare June 4, 2025 20:54
@carlaKC
Copy link
Contributor Author

carlaKC commented Jun 4, 2025

Rebased + addressed nit.

tankyleo
tankyleo previously approved these changes Jun 4, 2025
Copy link

codecov bot commented Jun 4, 2025

Codecov Report

Attention: Patch coverage is 95.78313% with 14 lines in your changes missing coverage. Please review.

Project coverage is 89.93%. Comparing base (7b62ea4) to head (99c645e).

Files with missing lines Patch % Lines
lightning/src/ln/channel.rs 93.02% 9 Missing ⚠️
lightning/src/ln/functional_tests.rs 94.11% 2 Missing and 1 partial ⚠️
lightning/src/ln/channelmanager.rs 98.56% 1 Missing and 1 partial ⚠️
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.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

Copy link
Collaborator

@TheBlueMatt TheBlueMatt left a 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.

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());
Copy link
Collaborator

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).

Copy link
Contributor Author

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 🤦‍♀️

carlaKC and others added 7 commits June 6, 2025 11:14
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.
// 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());
Copy link
Contributor Author

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

@carlaKC
Copy link
Contributor Author

carlaKC commented Jun 6, 2025

Removed asserts + moved supports_anchors_nonzero_fee_htlc_tx assert, diff here.

@carlaKC carlaKC requested review from TheBlueMatt and tankyleo June 6, 2025 16:37
@TheBlueMatt TheBlueMatt merged commit 0430b1e into lightningdevkit:main Jun 6, 2025
25 of 26 checks passed
@wpaulino wpaulino removed their request for review June 6, 2025 21:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants