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

Dual-funding: permit re-negotiation of require-confirmed on RBFs #6945

Merged
merged 2 commits into from Feb 11, 2024

Conversation

niftynei
Copy link
Collaborator

@niftynei niftynei commented Dec 14, 2023

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

Copy link
Collaborator

@ddustin ddustin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks great! ACK 82749ff

@cdecker cdecker added this to the v24.02 milestone Feb 8, 2024
niftynei and others added 2 commits February 9, 2024 18:14
We now require peers to reaffirm their preference for
`require_confirmed_inputs` when executing an RBF.

Requested-By: @t-bast
@cdecker cdecker merged commit 89c7cad into ElementsProject:master Feb 11, 2024
36 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants