1 namespace org { namespace ldk { namespace enums {/**
2 * An enum that represents the priority at which we want a transaction to confirm used for feerate
5 public enum ConfirmationTarget {
7 * We have some funds available on chain which we need to spend prior to some expiry time at
8 * which point our counterparty may be able to steal them. Generally we have in the high tens
9 * to low hundreds of blocks to get our transaction on-chain, but we shouldn't risk too low a
10 * fee - this should be a relatively high priority feerate.
12 LDKConfirmationTarget_OnChainSweep,
14 * This is the lowest feerate we will allow our channel counterparty to have in an anchor
15 * channel in order to close the channel if a channel party goes away.
17 * This needs to be sufficient to get into the mempool when the channel needs to
18 * be force-closed. Setting too high may result in force-closures if our counterparty attempts
19 * to use a lower feerate. Because this is for anchor channels, we can always bump the feerate
20 * later; the feerate here only needs to be sufficient to enter the mempool.
22 * A good estimate is the expected mempool minimum at the time of force-closure. Obviously this
23 * is not an estimate which is very easy to calculate because we do not know the future. Using
24 * a simple long-term fee estimate or tracking of the mempool minimum is a good approach to
25 * ensure you can always close the channel. A future change to Bitcoin's P2P network
26 * (package relay) may obviate the need for this entirely.
28 LDKConfirmationTarget_MinAllowedAnchorChannelRemoteFee,
30 * The lowest feerate we will allow our channel counterparty to have in a non-anchor channel.
32 * This is the feerate on the transaction which we (or our counterparty) will broadcast in
33 * order to close the channel if a channel party goes away. Setting this value too high will
34 * cause immediate force-closures in order to avoid having an unbroadcastable state.
36 * This feerate represents the fee we pick now, which must be sufficient to enter a block at an
37 * arbitrary time in the future. Obviously this is not an estimate which is very easy to
38 * calculate. This can leave channels subject to being unable to close if feerates rise, and in
39 * general you should prefer anchor channels to ensure you can increase the feerate when the
40 * transactions need broadcasting.
42 * Do note some fee estimators round up to the next full sat/vbyte (ie 250 sats per kw),
43 * causing occasional issues with feerate disagreements between an initiator that wants a
44 * feerate of 1.1 sat/vbyte and a receiver that wants 1.1 rounded up to 2. If your fee
45 * estimator rounds subtracting 250 to your desired feerate here can help avoid this issue.
47 * [`ChannelConfig::max_dust_htlc_exposure`]: crate::util::config::ChannelConfig::max_dust_htlc_exposure
49 LDKConfirmationTarget_MinAllowedNonAnchorChannelRemoteFee,
51 * This is the feerate on the transaction which we (or our counterparty) will broadcast in
52 * order to close the channel if a channel party goes away.
54 * This needs to be sufficient to get into the mempool when the channel needs to
55 * be force-closed. Setting too low may result in force-closures. Because this is for anchor
56 * channels, it can be a low value as we can always bump the feerate later.
58 * A good estimate is the expected mempool minimum at the time of force-closure. Obviously this
59 * is not an estimate which is very easy to calculate because we do not know the future. Using
60 * a simple long-term fee estimate or tracking of the mempool minimum is a good approach to
61 * ensure you can always close the channel. A future change to Bitcoin's P2P network
62 * (package relay) may obviate the need for this entirely.
64 LDKConfirmationTarget_AnchorChannelFee,
66 * Lightning is built around the ability to broadcast a transaction in the future to close our
67 * channel and claim all pending funds. In order to do so, non-anchor channels are built with
68 * transactions which we need to be able to broadcast at some point in the future.
70 * This feerate represents the fee we pick now, which must be sufficient to enter a block at an
71 * arbitrary time in the future. Obviously this is not an estimate which is very easy to
72 * calculate, so most lightning nodes use some relatively high-priority feerate using the
73 * current mempool. This leaves channels subject to being unable to close if feerates rise, and
74 * in general you should prefer anchor channels to ensure you can increase the feerate when the
75 * transactions need broadcasting.
77 * Since this should represent the feerate of a channel close that does not need fee
78 * bumping, this is also used as an upper bound for our attempted feerate when doing cooperative
79 * closure of any channel.
81 LDKConfirmationTarget_NonAnchorChannelFee,
83 * When cooperatively closing a channel, this is the minimum feerate we will accept.
84 * Recommended at least within a day or so worth of blocks.
86 * This will also be used when initiating a cooperative close of a channel. When closing a
87 * channel you can override this fee by using
88 * [`ChannelManager::close_channel_with_feerate_and_script`].
90 * [`ChannelManager::close_channel_with_feerate_and_script`]: crate::ln::channelmanager::ChannelManager::close_channel_with_feerate_and_script
92 LDKConfirmationTarget_ChannelCloseMinimum,