Skip to content

Conversation

@arik-so
Copy link

@arik-so arik-so commented Jul 17, 2023

No description provided.

Roasbeef and others added 28 commits May 29, 2022 17:57
+ script layout and readability
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 Roasbeef force-pushed the simple-taproot-chans branch from e95e7ac to e25132d Compare August 24, 2023 01:05
@Roasbeef Roasbeef force-pushed the simple-taproot-chans branch from 1ad02ee to 4c1314a Compare July 10, 2025 23:58
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.

3 participants