[Java] Update auto-generated bindings

Author: TheBlueMatt

src/main/java/org/ldk/enums/BalanceSource.java

@@ -0,0 +1,26 @@
+package org.ldk.enums;
+
+/**
+ * Indicates whether the balance is derived from a cooperative close, a force-close
+ * (for holder or counterparty), or whether it is for an HTLC.
+ */
+public enum BalanceSource {
+	/**
+	 * The channel was force closed by the holder.
+	 */
+	LDKBalanceSource_HolderForceClosed,
+	/**
+	 * The channel was force closed by the counterparty.
+	 */
+	LDKBalanceSource_CounterpartyForceClosed,
+	/**
+	 * The channel was cooperatively closed.
+	 */
+	LDKBalanceSource_CoopClose,
+	/**
+	 * This balance is the result of an HTLC.
+	 */
+	LDKBalanceSource_Htlc,
+	; static native void init();
+	static { org.ldk.impl.bindings.run_statics(); init(); }
+}

src/main/java/org/ldk/enums/Bolt12SemanticError.java

@@ -112,6 +112,10 @@ public enum Bolt12SemanticError {
 	 * An invoice payment hash was expected but was missing.
 	 */
 	LDKBolt12SemanticError_MissingPaymentHash,
+	/**
+	 * An invoice payment hash was provided but was not expected.
+	 */
+	LDKBolt12SemanticError_UnexpectedPaymentHash,
 	/**
 	 * A signature was expected but was missing.
 	 */

src/main/java/org/ldk/enums/ConfirmationTarget.java

@@ -5,13 +5,23 @@
  * estimation.
  */
 public enum ConfirmationTarget {
+	/**
+	 * The most aggressive (i.e. highest) feerate estimate available.
+	 * 
+	 * This is used to sanity-check our counterparty's feerates and should be as conservative as
+	 * possible to ensure that we don't confuse a peer using a very conservative estimator for one
+	 * trying to burn channel balance to dust.
+	 */
+	LDKConfirmationTarget_MaximumFeeEstimate,
 	/**
 	 * We have some funds available on chain which we need to spend prior to some expiry time at
-	 * which point our counterparty may be able to steal them. Generally we have in the high tens
-	 * to low hundreds of blocks to get our transaction on-chain, but we shouldn't risk too low a
-	 * fee - this should be a relatively high priority feerate.
+	 * which point our counterparty may be able to steal them.
+	 * 
+	 * Generally we have in the high tens to low hundreds of blocks to get our transaction
+	 * on-chain (it doesn't have to happen in the next few blocks!), but we shouldn't risk too low
+	 * a fee - this should be a relatively high priority feerate.
 	 */
-	LDKConfirmationTarget_OnChainSweep,
+	LDKConfirmationTarget_UrgentOnChainSweep,
 	/**
 	 * This is the lowest feerate we will allow our channel counterparty to have in an anchor
 	 * channel in order to close the channel if a channel party goes away.
@@ -93,14 +103,18 @@ public enum ConfirmationTarget {
 	 */
 	LDKConfirmationTarget_ChannelCloseMinimum,
 	/**
-	 * The feerate [`OutputSweeper`] will use on transactions spending
-	 * [`SpendableOutputDescriptor`]s after a channel closure.
+	 * The feerate used to claim on-chain funds when there is no particular urgency to do so.
+	 * 
+	 * It is used to get commitment transactions without any HTLCs confirmed in [`ChannelMonitor`]
+	 * and by  [`OutputSweeper`] 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.
 	 * 
+	 * [`ChannelMonitor`]: crate::chain::channelmonitor::ChannelMonitor
 	 * [`OutputSweeper`]: crate::util::sweep::OutputSweeper
 	 * [`SpendableOutputDescriptor`]: crate::sign::SpendableOutputDescriptor
 	 */

src/main/java/org/ldk/enums/CreationError.java

@@ -21,16 +21,11 @@ public enum CreationError {
 	 */
 	LDKCreationError_InvalidAmount,
 	/**
-	 * Route hints were required for this invoice and were missing. Applies to
-	 * [phantom invoices].
-	 * 
-	 * [phantom invoices]: crate::utils::create_phantom_invoice
+	 * Route hints were required for this invoice and were missing.
 	 */
 	LDKCreationError_MissingRouteHints,
 	/**
-	 * The provided `min_final_cltv_expiry_delta` was less than [`MIN_FINAL_CLTV_EXPIRY_DELTA`].
-	 * 
-	 * [`MIN_FINAL_CLTV_EXPIRY_DELTA`]: lightning::ln::channelmanager::MIN_FINAL_CLTV_EXPIRY_DELTA
+	 * The provided `min_final_cltv_expiry_delta` was less than rust-lightning's minimum.
 	 */
 	LDKCreationError_MinFinalCltvExpiryDeltaTooShort,
 	; static native void init();

src/main/java/org/ldk/enums/Direction.java

@@ -1,8 +1,8 @@
 package org.ldk.enums;
 
 /**
- * The side of a channel that is the [`IntroductionNode`] in a [`BlindedPath`]. [BOLT 7] defines
- * which nodes is which in the [`ChannelAnnouncement`] message.
+ * The side of a channel that is the [`IntroductionNode`] in a blinded path. [BOLT 7] defines which
+ * nodes is which in the [`ChannelAnnouncement`] message.
  * 
  * [BOLT 7]: https://github.com/lightning/bolts/blob/master/07-routing-gossip.md#the-channel_announcement-message
  * [`ChannelAnnouncement`]: crate::ln::msgs::ChannelAnnouncement

src/main/java/org/ldk/enums/InboundHTLCStateDetails.java

@@ -0,0 +1,51 @@
+package org.ldk.enums;
+
+/**
+ * Exposes the state of pending inbound HTLCs.
+ * 
+ * At a high level, an HTLC being forwarded from one Lightning node to another Lightning node goes
+ * through the following states in the state machine:
+ * - Announced for addition by the originating node through the update_add_htlc message.
+ * - Added to the commitment transaction of the receiving node and originating node in turn
+ * through the exchange of commitment_signed and revoke_and_ack messages.
+ * - Announced for resolution (fulfillment or failure) by the receiving node through either one of
+ * the update_fulfill_htlc, update_fail_htlc, and update_fail_malformed_htlc messages.
+ * - Removed from the commitment transaction of the originating node and receiving node in turn
+ * through the exchange of commitment_signed and revoke_and_ack messages.
+ * 
+ * This can be used to inspect what next message an HTLC is waiting for to advance its state.
+ */
+public enum InboundHTLCStateDetails {
+	/**
+	 * We have added this HTLC in our commitment transaction by receiving commitment_signed and
+	 * returning revoke_and_ack. We are awaiting the appropriate revoke_and_ack's from the remote
+	 * before this HTLC is included on the remote commitment transaction.
+	 */
+	LDKInboundHTLCStateDetails_AwaitingRemoteRevokeToAdd,
+	/**
+	 * This HTLC has been included in the commitment_signed and revoke_and_ack messages on both sides
+	 * and is included in both commitment transactions.
+	 * 
+	 * This HTLC is now safe to either forward or be claimed as a payment by us. The HTLC will
+	 * remain in this state until the forwarded upstream HTLC has been resolved and we resolve this
+	 * HTLC correspondingly, or until we claim it as a payment. If it is part of a multipart
+	 * payment, it will only be claimed together with other required parts.
+	 */
+	LDKInboundHTLCStateDetails_Committed,
+	/**
+	 * We have received the preimage for this HTLC and it is being removed by fulfilling it with
+	 * update_fulfill_htlc. This HTLC is still on both commitment transactions, but we are awaiting
+	 * the appropriate revoke_and_ack's from the remote before this HTLC is removed from the remote
+	 * commitment transaction after update_fulfill_htlc.
+	 */
+	LDKInboundHTLCStateDetails_AwaitingRemoteRevokeToRemoveFulfill,
+	/**
+	 * The HTLC is being removed by failing it with update_fail_htlc or update_fail_malformed_htlc.
+	 * This HTLC is still on both commitment transactions, but we are awaiting the appropriate
+	 * revoke_and_ack's from the remote before this HTLC is removed from the remote commitment
+	 * transaction.
+	 */
+	LDKInboundHTLCStateDetails_AwaitingRemoteRevokeToRemoveFail,
+	; static native void init();
+	static { org.ldk.impl.bindings.run_statics(); init(); }
+}

src/main/java/org/ldk/enums/OutboundHTLCStateDetails.java

@@ -0,0 +1,48 @@
+package org.ldk.enums;
+
+/**
+ * Exposes the state of pending outbound HTLCs.
+ * 
+ * At a high level, an HTLC being forwarded from one Lightning node to another Lightning node goes
+ * through the following states in the state machine:
+ * - Announced for addition by the originating node through the update_add_htlc message.
+ * - Added to the commitment transaction of the receiving node and originating node in turn
+ * through the exchange of commitment_signed and revoke_and_ack messages.
+ * - Announced for resolution (fulfillment or failure) by the receiving node through either one of
+ * the update_fulfill_htlc, update_fail_htlc, and update_fail_malformed_htlc messages.
+ * - Removed from the commitment transaction of the originating node and receiving node in turn
+ * through the exchange of commitment_signed and revoke_and_ack messages.
+ * 
+ * This can be used to inspect what next message an HTLC is waiting for to advance its state.
+ */
+public enum OutboundHTLCStateDetails {
+	/**
+	 * We are awaiting the appropriate revoke_and_ack's from the remote before the HTLC is added
+	 * on the remote's commitment transaction after update_add_htlc.
+	 */
+	LDKOutboundHTLCStateDetails_AwaitingRemoteRevokeToAdd,
+	/**
+	 * The HTLC has been added to the remote's commitment transaction by sending commitment_signed
+	 * and receiving revoke_and_ack in return.
+	 * 
+	 * The HTLC will remain in this state until the remote node resolves the HTLC, or until we
+	 * unilaterally close the channel due to a timeout with an uncooperative remote node.
+	 */
+	LDKOutboundHTLCStateDetails_Committed,
+	/**
+	 * The HTLC has been fulfilled successfully by the remote with a preimage in update_fulfill_htlc,
+	 * and we removed the HTLC from our commitment transaction by receiving commitment_signed and
+	 * returning revoke_and_ack. We are awaiting the appropriate revoke_and_ack's from the remote
+	 * for the removal from its commitment transaction.
+	 */
+	LDKOutboundHTLCStateDetails_AwaitingRemoteRevokeToRemoveSuccess,
+	/**
+	 * The HTLC has been failed by the remote with update_fail_htlc or update_fail_malformed_htlc,
+	 * and we removed the HTLC from our commitment transaction by receiving commitment_signed and
+	 * returning revoke_and_ack. We are awaiting the appropriate revoke_and_ack's from the remote
+	 * for the removal from its commitment transaction.
+	 */
+	LDKOutboundHTLCStateDetails_AwaitingRemoteRevokeToRemoveFailure,
+	; static native void init();
+	static { org.ldk.impl.bindings.run_statics(); init(); }
+}

src/main/java/org/ldk/enums/PaymentFailureReason.java

@@ -6,6 +6,12 @@
 public enum PaymentFailureReason {
 	/**
 	 * The intended recipient rejected our payment.
+	 * 
+	 * Also used for [`UnknownRequiredFeatures`] and [`InvoiceRequestRejected`] when downgrading to
+	 * version prior to 0.0.124.
+	 * 
+	 * [`UnknownRequiredFeatures`]: Self::UnknownRequiredFeatures
+	 * [`InvoiceRequestRejected`]: Self::InvoiceRequestRejected
 	 */
 	LDKPaymentFailureReason_RecipientRejected,
 	/**
@@ -27,7 +33,10 @@ public enum PaymentFailureReason {
 	 * The payment expired while retrying, based on the provided
 	 * [`PaymentParameters::expiry_time`].
 	 * 
+	 * Also used for [`InvoiceRequestExpired`] when downgrading to version prior to 0.0.124.
+	 * 
 	 * [`PaymentParameters::expiry_time`]: crate::routing::router::PaymentParameters::expiry_time
+	 * [`InvoiceRequestExpired`]: Self::InvoiceRequestExpired
 	 */
 	LDKPaymentFailureReason_PaymentExpired,
 	/**
@@ -43,6 +52,20 @@ public enum PaymentFailureReason {
 	 * your router.
 	 */
 	LDKPaymentFailureReason_UnexpectedError,
+	/**
+	 * An invoice was received that required unknown features.
+	 */
+	LDKPaymentFailureReason_UnknownRequiredFeatures,
+	/**
+	 * A [`Bolt12Invoice`] was not received in a reasonable amount of time.
+	 */
+	LDKPaymentFailureReason_InvoiceRequestExpired,
+	/**
+	 * An [`InvoiceRequest`] for the payment was rejected by the recipient.
+	 * 
+	 * [`InvoiceRequest`]: crate::offers::invoice_request::InvoiceRequest
+	 */
+	LDKPaymentFailureReason_InvoiceRequestRejected,
 	; static native void init();
 	static { org.ldk.impl.bindings.run_statics(); init(); }
 }

src/main/java/org/ldk/enums/RetryableSendFailure.java

@@ -29,6 +29,14 @@ public enum RetryableSendFailure {
 	 * [`Event::PaymentFailed`]: crate::events::Event::PaymentFailed
 	 */
 	LDKRetryableSendFailure_DuplicatePayment,
+	/**
+	 * The [`RecipientOnionFields::payment_metadata`], [`RecipientOnionFields::custom_tlvs`], or
+	 * [`BlindedPaymentPath`]s provided are too large and caused us to exceed the maximum onion
+	 * packet size of 1300 bytes.
+	 * 
+	 * [`BlindedPaymentPath`]: crate::blinded_path::payment::BlindedPaymentPath
+	 */
+	LDKRetryableSendFailure_OnionPacketSizeExceeded,
 	; static native void init();
 	static { org.ldk.impl.bindings.run_statics(); init(); }
 }

src/main/java/org/ldk/enums/Secp256k1Error.java

@@ -48,6 +48,10 @@ public enum Secp256k1Error {
 	 * The only valid parity values are 0 or 1.
 	 */
 	LDKSecp256k1Error_InvalidParityValue,
+	/**
+	 * Invalid Elligator Swift Value
+	 */
+	LDKSecp256k1Error_InvalidEllSwift,
 	; static native void init();
 	static { org.ldk.impl.bindings.run_statics(); init(); }
 }