forked from lightning/bolts
-
Notifications
You must be signed in to change notification settings - Fork 2
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
Use built-in MermaidJS renderer #7
Open
arik-so
wants to merge
28
commits into
Roasbeef:simple-taproot-chans
Choose a base branch
from
arik-so:taproot-mermaid
base: simple-taproot-chans
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Conversation
This file contains 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
+ script layout and readability
fix and make scripts smaller
We'll just re-use the funding key instead. Alternatively, we could use the _other_ party's key here.
Doesn't add anything atm, so might as well drop it.
This also adds the new partial signature encoding which uses the final nonce which is needed for final signature combination.
In this commit, we build off the prior JIT nonce proposal modifying the following: * The funding flow returns to being symmetric. Both `open_channel` and `accept_channel` carry nonces. * The `shutdown` message once again transmit a nonce that'll be used by both sides to sign the shutdown transaction. A symmetric nonce approach is used here as both sides already know what the other will use for their nonce, and there's only a single message to sign. * The `closing_signed` message now only carries a 32-byte `partial_sig` value, as the nonces has already been transmitted ahead of time. Additionally, the existing "negotiation" feature has been done away with. Cooperative close will now always succeed after a single round, as the initiator is the only that ultimately pays fees.
bolt-simple-taproot: make funding symmetric, add new type for shutdown
A NUMs point means we can do normal recovery scans for a remote output like we do today.
In this commit, we modify the to_loccal revocation path to use the existing NUMs point to force all sweeps via a tapscript reveal. This ensures that the internal key is always revealed so the anchor output can always be swept.
Clarify + simplicity over cleverness
…pdates bolt-simple-taproot: restore NUMs point usage
…reated`. This still allows the cosigner to verify that the initiator is valid to generate a valid musig2 partial signature, and allows for the local nonces to more closely mimic JIT behavior.
Roasbeef
force-pushed
the
simple-taproot-chans
branch
from
August 24, 2023 01:05
e95e7ac
to
e25132d
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
No description provided.