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

diff --git a/lightning/src/util/config.rs b/lightning/src/util/config.rs
index 54ea6178..f44e43b7 100644
--- a/lightning/src/util/config.rs
+++ b/lightning/src/util/config.rs
@@ -274,7 +274,7 @@ impl Default for ChannelHandshakeLimits {
 
 /// Options which apply on a per-channel basis and may change at runtime or based on negotiation
 /// with our counterparty.
-#[derive(Copy, Clone, Debug, PartialEq)]
+#[derive(Copy, Clone, Debug, PartialEq, Eq)]
 pub struct ChannelConfig {
 	/// Amount (in millionths of a satoshi) charged per satoshi for payments forwarded outbound
 	/// over the channel.
@@ -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