[C#] Update auto-generated bindings to LDK 0.0.123

[ldk-java] / c_sharp / src / org / ldk / enums / ConfirmationTarget.cs

diff --git a/c_sharp/src/org/ldk/enums/ConfirmationTarget.cs b/c_sharp/src/org/ldk/enums/ConfirmationTarget.cs
index c5b9fcde15d2c417b77892d5da4efed1fac2b78b..d2a4d73a0343450cb687bf976f8c88819ecdbfc5 100644 (file)
--- a/c_sharp/src/org/ldk/enums/ConfirmationTarget.cs
+++ b/c_sharp/src/org/ldk/enums/ConfirmationTarget.cs
@@ -90,4 +90,17 @@ public enum ConfirmationTarget {
         * [`ChannelManager::close_channel_with_feerate_and_script`]: crate::ln::channelmanager::ChannelManager::close_channel_with_feerate_and_script
         */
        LDKConfirmationTarget_ChannelCloseMinimum,
+       /**
+        * The feerate [`OutputSweeper`] will use on transactions spending
+        * [`SpendableOutputDescriptor`]s after a channel closure.
+        * 
+        * Generally spending these outputs is safe as long as they eventually confirm, so a value
+        * (slightly above) the mempool minimum should suffice. However, as this value will influence
+        * how long funds will be unavailable after channel closure, [`FeeEstimator`] implementors
+        * might want to choose a higher feerate to regain control over funds faster.
+        * 
+        * [`OutputSweeper`]: crate::util::sweep::OutputSweeper
+        * [`SpendableOutputDescriptor`]: crate::sign::SpendableOutputDescriptor
+        */
+       LDKConfirmationTarget_OutputSpendingFee,
 }} } }