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.

Sign up for GitHub

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

Jump to bottom

Allow splicing on non dual-funded channels #2727

Merged
merged 2 commits into from
Sep 26, 2023
Merged

Allow splicing on non dual-funded channels #2727

merged 2 commits into from
Sep 26, 2023

Commits on Sep 26, 2023

  1. Allow splicing on non dual-funded channels 

    We currently allow splicing on top of a channel that was created without
using dual funding, but it results in an incorrect channel reserve being
used post-splice.
    @t-bast
    t-bast committed Sep 26, 2023
    Configuration menu
    Copy the full SHA
    158259a View commit details
    Browse the repository at this point in the history

  2. Rename requestedChannelReserve_opt 

    This field only applies to the first funding index, so we rename it to
make that explicit. Once a splice has happened, it will be ignored.
    @t-bast
    t-bast committed Sep 26, 2023
    Configuration menu
    Copy the full SHA
    a061f2f View commit details
    Browse the repository at this point in the history