-
Notifications
You must be signed in to change notification settings - Fork 1
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
splice: signer must be informed of splice params #5
Conversation
63b0590
to
defead9
Compare
/* We calculcate the `push_value` to send to the | ||
* hsmd, that is the remote amount in the channel | ||
* after the splice. */ | ||
switch (our_role) { |
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.
this is hard to analyze, because our_role
is used to calculate opener
, but then both opener
and our_role
are used in the logic below. it would be best to use only one or the other.
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.
Ok this should be solved in the last version of the commit, let me know if this help
defead9
to
c3b56e7
Compare
The signer needs to know when the splice operation starts and the splice parameters for each splice transaction candidate. The channel establishment v2 (dual funding) code path already notifies the signer via the hsmd API hsmd_ready_channel calls However, the splicing code path does not. Link: ElementsProject#6723 Suggested-by: @devrandom Co-Developed-by: @devrandom Co-Developed-by: Ken Sedgwick <[email protected]> Signed-off-by: Vincenzo Palazzo <[email protected]>
c3b56e7
to
cf18fa6
Compare
Moving this upstream! |
Pre-review before opening a draft PR to cln