Dual-funding: permit re-negotiation of require-confirmed on RBFs #6945
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.
Be explicit about the
require-confirmed
requirements for RBFs as well as initial txs.Updates CLN to conform to the latest spec draft, including lightning/bolts@27ffef4
Be explicit about the require-confirmed requirements for RBFs as well as initial txs.
Initially we were re-using the value at start for any subsequent renegotiations, but with this patch we
now use whatever the system-wide setting is at the time that we attempt an RBF. This makes it easier to test
and allows you to (with some effort) update what channels request at a system level.
Requested-By: @t-bast