lncfg: add new protocol option - RbfCoopClose

lncfg/protocol.go

@@ -35,6 +35,10 @@ type ProtocolOptions struct {
 	// the experimental taproot overlay chan type.
 	TaprootOverlayChans bool `long:"simple-taproot-overlay-chans" description:"if set, then lnd will create and accept requests for channels using the taproot overlay commitment type"`
 
+	// RbfCoopClose should be set if we want to signal that we support for
+	// the new experimental RBF coop close feature.
+	RbfCoopClose bool `long:"rbf-coop-close" description:"if set, then lnd will signal that it supports the new RBF based coop close protocol"`
+
 	// NoAnchors should be set if we don't want to support opening or accepting
 	// channels having the anchor commitment type.
 	NoAnchors bool `long:"no-anchors" description:"disable support for anchor commitments"`

lncfg/protocol_integration.go

@@ -41,6 +41,10 @@ type ProtocolOptions struct {
 	// TODO(halseth): transition itests to anchors instead!
 	Anchors bool `long:"anchors" description:"enable support for anchor commitments"`
 
+	// RbfCoopClose should be set if we want to signal that we support for
+	// the new experimental RBF coop close feature.
+	RbfCoopClose bool `long:"rbf-coop-close" description:"if set, then lnd will signal that it supports the new RBF based coop close protocol"`
+
 	// ScriptEnforcedLease enables script enforced commitments for channel
 	// leases.
 	//

sample-lnd.conf

@@ -1413,6 +1413,9 @@
 ; Set to disable experimental endorsement signaling.
 ; protocol.no-experimental-endorsement=false
 
+; Set to disable support for RBF based coop close.
+; protocol.rbf-coop-close=false
+
 ; Set to handle messages of a particular type that falls outside of the
 ; custom message number range (i.e. 513 is onion messages). Note that you can
 ; set this option as many times as you want to support more than one custom