Skip to content
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

multi: allow min-depth of zero for non-zero conf channels #8796

Merged
merged 2 commits into from
Jun 28, 2024

Conversation

ellemouton
Copy link
Collaborator

@ellemouton ellemouton commented May 30, 2024

If our peer indicates to us that they are OK with a zero conf channel (ie, they trust us) by setting min-depth to 0 in accept_channel, then as long as they support SCID aliases, we should just upgrade the channel to ZeroConf and continue the funding flow.

EDIT: updated to just allow the peer to set min-depth to 0. We dont upgrade the channel type.

Fixes #8783

NOTE: we already allow ourselves to do this when our peer sends us an OpenChannel without a zero-conf channel type:

lnd/funding/manager.go

Lines 1570 to 1583 in fed7609

if !zeroConf && acceptorResp.ZeroConf {
if !scidFeatureVal {
// Fail the funding flow.
flowErr := fmt.Errorf("scid-alias feature " +
"must be negotiated for zero-conf")
log.Errorf("Cancelling funding flow for "+
"zero-conf channel %v: %v", cid,
flowErr)
f.failFundingFlow(peer, cid, flowErr)
return
}
// Set zeroConf to true to enable the zero-conf flow.
zeroConf = true

So all this PR does is allow our peer to do this too :)

Copy link
Contributor

coderabbitai bot commented May 30, 2024

Important

Review skipped

Auto reviews are limited to specific labels.

Labels to auto review (1)
  • llm-review

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share
Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

channeldb/channel.go Outdated Show resolved Hide resolved
@ellemouton ellemouton requested a review from Crypt-iQ May 30, 2024 20:56
channeldb/channel.go Outdated Show resolved Hide resolved

// Zero conf channels will require an SCID alias, so request one
// now and add it to the reservation.
aliasScid, err := f.cfg.AliasManager.RequestAlias()
Copy link
Collaborator

Choose a reason for hiding this comment

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

👍

@saubyk saubyk added this to the v0.18.1 milestone Jun 3, 2024
@ellemouton
Copy link
Collaborator Author

hmmm ok from this comment on the original issue, it sounds like we dont actually need to go and change this to a zero conf channel. We can just allow them to send a min-depth of 0 (even though this is not a zero conf channel) and then we just continue as normal (and only send channel_ready when we see fit).

so the diff can actually be way smaller

cc @Crypt-iQ - wdyt?

@Crypt-iQ
Copy link
Collaborator

hmmm ok from this comment on the original issue, it sounds like we dont actually need to go and change this to a zero conf channel. We can just allow them to send a min-depth of 0 (even though this is not a zero conf channel) and then we just continue as normal (and only send channel_ready when we see fit).

so the diff can actually be way smaller

cc @Crypt-iQ - wdyt?

yup that seems fine

@ellemouton
Copy link
Collaborator Author

Ok I've made the update discussed above.

It's hard to write a test for this case cause we dont really support this between two LND nodes opening a non-zero conf channel cause we want to register for confirmations and this is not allowed with a depth of 0.

So to test this you can apply this patch which allows our channel acceptor to set a MinDepth of 0 & also makes sure we still register for 1 conf if we are on the receiver side of this operation. Then to actually test the flow, you can run the scid_alias_channel_update/public_no-chan-type_update test which uses the channel acceptor to open a non zero conf channel

@ellemouton ellemouton changed the title multi: allow implicit zero conf channels multi: allow min-depth of zero for non-zero conf channels Jun 14, 2024
@ellemouton ellemouton requested a review from Crypt-iQ June 14, 2024 20:03
@lightninglabs-deploy
Copy link

@Crypt-iQ: review reminder

@saubyk saubyk added the P2 should be fixed if one has time label Jun 25, 2024
Copy link
Collaborator

@yyforyongyu yyforyongyu left a comment

Choose a reason for hiding this comment

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

Needs a rebase, otherwise LGTM🌊

Even if the channel type is not zero conf. We will still use a min depth
of at least 1. We just dont fail if our peer indicates trust.
@ellemouton ellemouton merged commit 71ba355 into lightningnetwork:master Jun 28, 2024
30 of 34 checks passed
@ellemouton ellemouton deleted the acceptImplicitZeroConf branch June 28, 2024 14:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P2 should be fixed if one has time zero conf
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[bug]: Channels without zero-conf feature but minimum_depth 0 are rejected
5 participants