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

[7/?] - funding: update funding manager w/ new musig2+taproot funding flow #7346

Commits on Jul 26, 2023

  1. Configuration menu
    Copy the full SHA
    bc65546 View commit details
    Browse the repository at this point in the history
  2. Configuration menu
    Copy the full SHA
    1804e03 View commit details
    Browse the repository at this point in the history
  3. funding+peer: add support for new musig2 channel funding flow

    In this commit, we add support for the new musig2 channel funding flow.
    This flow is identical to the existing flow, but not both sides need to
    exchange local nonces up front, and then signatures sent are now partial
    signatures instead of regular signatures.
    
    The funding manager also gains some new state of the local nonces it
    needs to generate in order to send the funding locked message, and also
    process the funding locked message from the remote party.
    
    In order to allow the funding manger to generate the nonces that need to
    be applied to each channel, then AddNewChannel method has been modified
    to accept a set of options that the peer will then use to bind the
    nonces to a new channel.
    Roasbeef committed Jul 26, 2023
    Configuration menu
    Copy the full SHA
    a6248ec View commit details
    Browse the repository at this point in the history
  4. routing+funding: add new makeFundingScript to support reg and taproot…

    … channels
    
    In this commit, we start to set _internally_ a new feature bit in the
    channel announcements we generate. As these taproot channels can only be
    unadvertised, this will never actually leak to the public network. The
    funding manager will then set this field to allow the router to properly
    validate these channels.
    Roasbeef committed Jul 26, 2023
    Configuration menu
    Copy the full SHA
    83fe896 View commit details
    Browse the repository at this point in the history
  5. Configuration menu
    Copy the full SHA
    b66d538 View commit details
    Browse the repository at this point in the history
  6. contractcourt: update chain watcher to understand the taproot pkscript

    In this commit, we update the chain watcher to be able to generate the
    correct pkScript so it can register for confirmation and spend
    notifications for taproot channels.
    Roasbeef committed Jul 26, 2023
    Configuration menu
    Copy the full SHA
    e46dae5 View commit details
    Browse the repository at this point in the history
  7. lnwallet: generate local nonces if non passed in for taproot chans

    This ensures that when loading the channel again after a normal chan
    reest, we generate the local nonces, which ensures we can then process
    nonces the remote party sends us in their chan reest message.
    Roasbeef committed Jul 26, 2023
    Configuration menu
    Copy the full SHA
    3555afb View commit details
    Browse the repository at this point in the history
  8. Configuration menu
    Copy the full SHA
    ed3becb View commit details
    Browse the repository at this point in the history
  9. contractcourt: for taproot channels, wait for conf in closeObserver

    This ensures that we end up playing the target output on chain for
    taproot channels.
    Roasbeef committed Jul 26, 2023
    Configuration menu
    Copy the full SHA
    b09c3db View commit details
    Browse the repository at this point in the history

Commits on Jul 27, 2023

  1. Configuration menu
    Copy the full SHA
    7bca374 View commit details
    Browse the repository at this point in the history
  2. Configuration menu
    Copy the full SHA
    ea25054 View commit details
    Browse the repository at this point in the history