-
Notifications
You must be signed in to change notification settings - Fork 412
Add unsafe_funding_transaction_generated
#3056
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
Closed
Closed
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
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.
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.
Oops, sorry for the confusion, my comment at #3024 (comment) wasn't really intended to be that we'd expect users to handle this crazy hacky indirection, but rather we could push the broadcast out via the
Event
described in that PR but just don't use a config knob and rather do it via a new channel funding method.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.
the goal of this pr is to introduce an "unsafe_funding_tx_generated" that wouldnt check if the witness data is empty (https://github.com/lightningdevkit/rust-lightning/pull/3056/files?diff=split&w=0#diff-645d12c7269d09caab57d2e0c1fd34f672ee259994c86ad4bad7f4da9183671cR4682) but call
batch_funding_transaction_generated_intern
directly.is it the only blocker for lightningdevkit/ldk-node#257.
Beside the top lines regarding unsafe, the docs are the same as the original
funding_tx_generated
.I see how both PRs are related and introduce two separate functions(which is fine as is) but could be used in the same scenario(ie payjoin) but I would like to get this one merged first and unblock the ldk-node pr and complete the funding signed pr afterwards if that makes sense..
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.
here is a usage reference https://github.com/lightningdevkit/ldk-node/pull/257/files#diff-08958d877a718a472ec0db9bebccd1c47c758b2c486440024be88c6702da2dcbR178
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.
Hmmm, it seems a bit weird to introduce this here and then rewrite it one PR later to do something totally different? ISTM we could land #3024 without it taking toooo long.