X-Git-Url: http://git.bitcoin.ninja/index.cgi?a=blobdiff_plain;f=lightning%2Fsrc%2Futil%2Fconfig.rs;fp=lightning%2Fsrc%2Futil%2Fconfig.rs;h=b2004df3e9cbd0c043c2b2ef184e538f267ea02a;hb=71f4749e1c0d48a916c1ba3b0631d7796f61c074;hp=54ea6178798d25a3e6103c39419b886632024ca9;hpb=d2a9ae0b8eb5bdb1724be0b8d398d0fdf9870266;p=rust-lightning

diff --git a/lightning/src/util/config.rs b/lightning/src/util/config.rs
index 54ea6178..b2004df3 100644
--- a/lightning/src/util/config.rs
+++ b/lightning/src/util/config.rs
@@ -325,6 +325,12 @@ pub struct ChannelConfig {
 	/// to such payments may be sustantial if there are many dust HTLCs present when the
 	/// channel is force-closed.
 	///
+	/// The dust threshold for each HTLC is based on the `dust_limit_satoshis` for each party in a
+	/// channel negotiated throughout the channel open process, along with the fees required to have
+	/// a broadcastable HTLC spending transaction. When a channel supports anchor outputs
+	/// (specifically the zero fee HTLC transaction variant), this threshold no longer takes into
+	/// account the HTLC transaction fee as it is zero.
+	///
 	/// 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