Cross channel Splice testing #8363
Open
Conversation
This file contains hidden or 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
ddustin
force-pushed
the
ddustin/cross_splice_testing
branch
6 times, most recently
from
4c4360f to
165e36b
Compare
Make the failure reason more clear by adding more information to the signature failure message.
We used to use a check on the active psbt to see if our splice signature was in it — but now we need to generate the signature early. So we have to add a field tracking if we’ve sent it and add it to the database, wire protocols, and inflight objects.
Use the new i_sent_sigs field to track if we’ve sent our peer our user sigs.
Previous behavior was to fail on abort when we have signatures in the inflight — change this behavior to fail on abort if we have sent our peer our signatures.
When doing a multi channel splice, we need to break the deadlock by signing the shared output early (even though it is not sent to the peer until later).
Add more information to funding issue failure messages when splicing
Adding verbose logging option to introspect into what interactive tx is doing with inputs.
When doing a cross channel splice, inputs move from having no SIGHASH to having SIGHASH_ALL assigned. This causes psbt_get_changeset to flag the input as having changed, as the sighash value is compared. This causes the second channel splice to `tx_remove_input` the input as it doesn’t match anymore, breaking the splice. We fix this by removing the sighash value from input comparisions.
Since the signature data may vary, we must copy the new psbt into splicing->current_psbt. This never occured during normal operation, but when doing a cross splice there may be vital signature(s) in the psbt that came from another splice that get dropped without this step.
A python test that splices into two channels at the same time with on transaction. Changelog-Added: Adding support for cross-channel splicing.
ddustin
force-pushed
the
ddustin/cross_splice_testing
branch
6 times, most recently
from
bb28681 to
deddba8
Compare
This should help debug failed ping responses showing up in CI.
ddustin
force-pushed
the
ddustin/cross_splice_testing
branch
4 times, most recently
from
1daf975 to
e13b398
Compare
ddustin
force-pushed
the
ddustin/cross_splice_testing
branch
from
e13b398 to
2c29e41
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.
Implemented a test for a splice-in into two channels at the same time using one transaction.
The test revealed three issues:
interactive-txdiffs a9d1dbfThis PR fixes those issues, adds a pytest for them, and makes basic two channel splices work, lets goooo 🔥