X-Git-Url: http://git.bitcoin.ninja/index.cgi?a=blobdiff_plain;f=lightning%2Fsrc%2Futil%2Fconfig.rs;h=55d506e79f145a386919ecce11f54ea7adbb432f;hb=0df247d6328ea78a6c1daa3d01f5c311e82f06a6;hp=2e9e8e036b5032d58a40d1748e92d1f70eb200cf;hpb=1bb9e64ebc6afaa21afcef4f71bb83054d9b2023;p=rust-lightning

diff --git a/lightning/src/util/config.rs b/lightning/src/util/config.rs
index 2e9e8e03..55d506e7 100644
--- a/lightning/src/util/config.rs
+++ b/lightning/src/util/config.rs
@@ -206,7 +206,46 @@ pub struct ChannelConfig {
 	/// This cannot be changed after a channel has been initialized.
 	///
 	/// Default value: true.
-	pub commit_upfront_shutdown_pubkey: bool
+	pub commit_upfront_shutdown_pubkey: bool,
+	/// Limit our total exposure to in-flight HTLCs which are burned to fees as they are too
+	/// small to claim on-chain.
+	///
+	/// When an HTLC present in one of our channels is below a "dust" threshold, the HTLC will
+	/// not be claimable on-chain, instead being turned into additional miner fees if either
+	/// party force-closes the channel. Because the threshold is per-HTLC, our total exposure
+	/// to such payments may be sustantial if there are many dust HTLCs present when the
+	/// channel is force-closed.
+	///
+	/// This limit is applied for sent, forwarded, and received HTLCs and limits the total
+	/// exposure across all three types per-channel. Setting this too low may prevent the
+	/// sending or receipt of low-value HTLCs on high-traffic nodes, and this limit is very
+	/// important to prevent stealing of dust HTLCs by miners.
+	///
+	/// Default value: 5_000_000 msat.
+	pub max_dust_htlc_exposure_msat: u64,
+	/// The additional fee we're willing to pay to avoid waiting for the counterparty's
+	/// `to_self_delay` to reclaim funds.
+	///
+	/// When we close a channel cooperatively with our counterparty, we negotiate a fee for the
+	/// closing transaction which both sides find acceptable, ultimately paid by the channel
+	/// funder/initiator.
+	///
+	/// When we are the funder, because we have to pay the channel closing fee, we bound the
+	/// acceptable fee by our [`Background`] and [`Normal`] fees, with the upper bound increased by
+	/// this value. Because the on-chain fee we'd pay to force-close the channel is kept near our
+	/// [`Normal`] feerate during normal operation, this value represents the additional fee we're
+	/// willing to pay in order to avoid waiting for our counterparty's to_self_delay to reclaim our
+	/// funds.
+	///
+	/// When we are not the funder, we require the closing transaction fee pay at least our
+	/// [`Background`] fee estimate, but allow our counterparty to pay as much fee as they like.
+	/// Thus, this value is ignored when we are not the funder.
+	///
+	/// Default value: 1000 satoshis.
+	///
+	/// [`Normal`]: crate::chain::chaininterface::ConfirmationTarget::Normal
+	/// [`Background`]: crate::chain::chaininterface::ConfirmationTarget::Background
+	pub force_close_avoidance_max_fee_satoshis: u64,
 }
 
 impl Default for ChannelConfig {
@@ -218,13 +257,17 @@ impl Default for ChannelConfig {
 			cltv_expiry_delta: 6 * 12, // 6 blocks/hour * 12 hours
 			announced_channel: false,
 			commit_upfront_shutdown_pubkey: true,
+			max_dust_htlc_exposure_msat: 5_000_000,
+			force_close_avoidance_max_fee_satoshis: 1000,
 		}
 	}
 }
 
 impl_writeable_tlv_based!(ChannelConfig, {
 	(0, forwarding_fee_proportional_millionths, required),
+	(1, max_dust_htlc_exposure_msat, (default_value, 5_000_000)),
 	(2, cltv_expiry_delta, required),
+	(3, force_close_avoidance_max_fee_satoshis, (default_value, 1000)),
 	(4, announced_channel, required),
 	(6, commit_upfront_shutdown_pubkey, required),
 	(8, forwarding_fee_base_msat, required),
@@ -259,6 +302,23 @@ pub struct UserConfig {
 	///
 	/// Default value: false.
 	pub accept_forwards_to_priv_channels: bool,
+	/// If this is set to false, we do not accept inbound requests to open a new channel.
+	/// Default value: true.
+	pub accept_inbound_channels: bool,
+	/// If this is set to true, the user needs to manually accept inbound requests to open a new
+	/// channel.
+	///
+	/// When set to true, [`Event::OpenChannelRequest`] will be triggered once a request to open a
+	/// new inbound channel is received through a [`msgs::OpenChannel`] message. In that case, a
+	/// [`msgs::AcceptChannel`] message will not be sent back to the counterparty node unless the
+	/// user explicitly chooses to accept the request.
+	///
+	/// Default value: false.
+	///
+	/// [`Event::OpenChannelRequest`]: crate::util::events::Event::OpenChannelRequest
+	/// [`msgs::OpenChannel`]: crate::ln::msgs::OpenChannel
+	/// [`msgs::AcceptChannel`]: crate::ln::msgs::AcceptChannel
+	pub manually_accept_inbound_channels: bool,
 }
 
 impl Default for UserConfig {
@@ -268,6 +328,8 @@ impl Default for UserConfig {
 			peer_channel_config_limits: ChannelHandshakeLimits::default(),
 			channel_options: ChannelConfig::default(),
 			accept_forwards_to_priv_channels: false,
+			accept_inbound_channels: true,
+			manually_accept_inbound_channels: false,
 		}
 	}
 }