Is your feature request related to a problem? Please describe.
Today the RBF chan closer doesn't observe/propagate the auxOutputs functional option like the legacy closing protocol does:
|
// Before we complete the cooperative close, we'll see if we |
|
// have any extra aux options. |
|
c.auxOutputs, err = c.auxCloseOutputs(remoteProposedFee) |
|
if err != nil { |
|
return noClosing, err |
|
} |
|
c.auxOutputs.WhenSome(func(outs AuxCloseOutputs) { |
|
closeOpts = append( |
|
closeOpts, lnwallet.WithExtraCloseOutputs( |
|
outs.ExtraCloseOutputs, |
|
), |
|
) |
|
closeOpts = append( |
|
closeOpts, lnwallet.WithCustomCoopSort( |
|
outs.CustomSort, |
|
), |
|
) |
|
}) |
Describe the solution you'd like
We should update the state transition in the new RBF closer to support this feature (permits > 1 output to the sender on a co-op close transaction).
Is your feature request related to a problem? Please describe.
Today the RBF chan closer doesn't observe/propagate the
auxOutputsfunctional option like the legacy closing protocol does:lnd/lnwallet/chancloser/chancloser.go
Lines 946 to 963 in b01f4e5
Describe the solution you'd like
We should update the state transition in the new RBF closer to support this feature (permits > 1 output to the sender on a co-op close transaction).