Add recommendation for dust_limit lower bound

330 sat is the default lower bound for P2WSH outputs.

02-peer-protocol.md

@@ -238,7 +238,11 @@ The receiving node MAY fail the channel if:
   - it considers `max_htlc_value_in_flight_msat` too small.
   - it considers `channel_reserve_satoshis` too large.
   - it considers `max_accepted_htlcs` too small.
-  - it considers `dust_limit_satoshis` too small and plans to rely on the sending node publishing its commitment transaction in the event of a data loss (see [message-retransmission](02-peer-protocol.md#message-retransmission)).
+  - it considers `dust_limit_satoshis` too small and plans to rely on the sending
+    node publishing its commitment transaction in the event of a data loss
+    (see [message-retransmission](02-peer-protocol.md#message-retransmission)).
+    A recommended lower bound is 330 satoshis, which matches the bitcoin network's
+    dust threshold for p2wsh outputs.
   - it considers `dust_limit_satoshis` too large.
 
 The receiving node MUST fail the channel if:
@@ -252,7 +256,7 @@ are not valid secp256k1 pubkeys in compressed format.
   - `dust_limit_satoshis` is greater than `channel_reserve_satoshis`.
   - the funder's amount for the initial commitment transaction is not sufficient for full [fee payment](03-transactions.md#fee-payment).
   - both `to_local` and `to_remote` amounts for the initial commitment transaction are less than or equal to `channel_reserve_satoshis` (see [BOLT 3](03-transactions.md#commitment-transaction-outputs)).
-  - `funding_satoshis` is greater than or equal to 2^24 and the receiver does not support `option_support_large_channel`. 
+  - `funding_satoshis` is greater than or equal to 2^24 and the receiver does not support `option_support_large_channel`.
 
 The receiving node MUST NOT:
   - consider funds received, using `push_msat`, to be received until the funding transaction has reached sufficient depth.