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

chancloser: implement the new option_simple_close co-op close flow #8153

Open
Roasbeef opened this issue Nov 7, 2023 · 0 comments
Open

chancloser: implement the new option_simple_close co-op close flow #8153

Roasbeef opened this issue Nov 7, 2023 · 0 comments
Assignees
Labels
bug Unintended code behaviour channel closing Related to the closing of channels cooperatively and uncooperatively intermediate Issues suitable for developers moderately familiar with the codebase and LN needs triage spec

Comments

@Roasbeef
Copy link
Member

Roasbeef commented Nov 7, 2023

We should implement the new restricted chan co-op close flow: lightning/bolts#1096. Details of the new closing flow can be found in the linked PR.

Once this is implemented, it should be using along side the final taproot chans feature bit by default. This gives us a clean way to update to both the finalized version, and also require this new co-op close flow.

Implementation wise, it may make sense to attempt to start from a clean slate (new state machine), so we can get a better feel of the total code surface area of this new variant vs the existing widely implemented co-op close flow.

@Roasbeef Roasbeef added bug Unintended code behaviour intermediate Issues suitable for developers moderately familiar with the codebase and LN channel closing Related to the closing of channels cooperatively and uncooperatively spec needs triage labels Nov 7, 2023
@Roasbeef Roasbeef self-assigned this Nov 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Unintended code behaviour channel closing Related to the closing of channels cooperatively and uncooperatively intermediate Issues suitable for developers moderately familiar with the codebase and LN needs triage spec
Projects
None yet
Development

No branches or pull requests

1 participant