-
Notifications
You must be signed in to change notification settings - Fork 265
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
Implement option_simple_close
#2747
Draft
t-bast
wants to merge
6
commits into
master
Choose a base branch
from
option-simple-close
base: master
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.
Draft
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
Codecov ReportAttention: Patch coverage is
❗ Your organization needs to install the Codecov GitHub app to enable full functionality. Additional details and impacted files@@ Coverage Diff @@
## master #2747 +/- ##
==========================================
- Coverage 86.30% 86.18% -0.13%
==========================================
Files 224 224
Lines 19867 20326 +459
Branches 795 805 +10
==========================================
+ Hits 17147 17517 +370
- Misses 2720 2809 +89
|
24 tasks
t-bast
force-pushed
the
option-simple-close
branch
2 times, most recently
from
September 22, 2023 15:58
77023c5
to
db7a79d
Compare
t-bast
force-pushed
the
option-simple-close
branch
2 times, most recently
from
October 4, 2023 09:45
a223c78
to
e05d16e
Compare
t-bast
force-pushed
the
option-simple-close
branch
from
January 16, 2024 14:24
e05d16e
to
57ae172
Compare
t-bast
force-pushed
the
option-simple-close
branch
from
March 27, 2024 14:55
3b6879b
to
4420858
Compare
t-bast
force-pushed
the
option-simple-close
branch
from
September 18, 2024 16:58
4420858
to
7fda599
Compare
t-bast
force-pushed
the
option-simple-close
branch
3 times, most recently
from
October 11, 2024 07:08
f8b957d
to
f0571b2
Compare
t-bast
force-pushed
the
option-simple-close
branch
from
October 18, 2024 06:45
f0571b2
to
623b371
Compare
t-bast
force-pushed
the
option-simple-close
branch
from
October 22, 2024 01:37
36ff0c3
to
3708ab9
Compare
This feature adds two new messages: - `closing_complete` sent after exchanging `shutdown` - `closing_sig` sent in response to `closing_complete`
The spec allows the closer to use an OP_RETURN output if their amount is too low when using `option_simple_close`.
We introduce a new `NEGOTIATING_SIMPLE` state where we exchange the `closing_complete` and `closing_sig` messages, and allow RBF-ing previous transactions and updating our closing script. We stay in that state until one of the transactions confirms, or a force close is detected. This is important to ensure we're able to correctly reconnect and negotiate RBF candidates. We keep this separate from the previous NEGOTIATING state to make it easier to remove support for the older mutual close protocols once we're confident the network has been upgraded.
t-bast
force-pushed
the
option-simple-close
branch
from
December 6, 2024 17:05
3708ab9
to
ea979aa
Compare
Whenever one side sends `shutdown`, we restart a signing round from scratch. To be compatible with future taproot channels, we require the receiver to also send `shutdown` before moving on to exchanging `closing_complete` and `closing_sig`. This will give nodes a message to exchange fresh musig2 nonces before producing signatures. On reconnection, we also restart a signing session from scratch and discard pending partial signatures.
Whenever we exchange `shutdown`, we now require that new closing txs are signed before allowing another `shutdown` message to be sent to start a new signing round. This creates more risk of deadlock when one side fails to send their sigs, where we'll need to disconnect to start a new signing round. But that shouldn't happen if nodes are honest and not buggy, so it probably doesn't matter. If nodes are buggy or malicious, we will need to force-close anyway.
t-bast
force-pushed
the
option-simple-close
branch
from
December 9, 2024 10:57
ea979aa
to
c45cf33
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.
Implement
option_simple_close
as defined in lightning/bolts#1096Hopefully this is the last time we change the mutual close protocol! And at some point that will let us entirely remove all the code supporting the two previous mutual close protocols (this is why I kept the code as separate as possible instead of trying to fit into the existing
NEGOTIATING
state).Note that this is a prerequisite for taproot channels: this protocol allows nodes to safely exchange nonces in
shutdown
andclosing_complete
to spend a musig2 channel output.