Add tx_signatures.tlvs field (splicing-specific field in dual funding message) #2991
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.
Two relatively small changes, in preparation for splicing:
New
tx_signatures.tlvs
field. This field is splicing-specific, and is used for exchanging signature on the previous funding tx, which is a shared input. The spec of this is still non-finalized, just like for the rest of the already-added splicing messages (spec PRs Add funding outpoint sigs to tx_signatures message lightning/bolts#1009 Splice draft (feature 62/63) lightning/bolts#863)Place all Splicing messages -- which are still only placeholders without real functionality -- behind the recently-introduced
dual_funding
feature flag. Splicing relies on dual funding, and is not usable without dual funding.Note: command for testing: