Rephrase the fee spike buffer requirement

lightning · Mar 30, 2020 · afb7313 · m-schmoock · Mar 30, 2020 · t-bast
1 parent f5490f1
commit afb7313
Showing 1 changed file with 4 additions and 4 deletions.
diff --git a/02-peer-protocol.md b/02-peer-protocol.md
@@ -793,10 +793,10 @@ A sending node:
     transaction at the current `feerate_per_kw` while maintaining its channel
     reserve (see [Updating Fees](#updating-fees-update_fee)).
     - SHOULD NOT offer `amount_msat` if, after adding that HTLC to its commitment
-    transaction, its remaining balance doesn't allow it to pay the fee for a
-    future additional non-dust HTLC at a higher feerate while maintaining its
-    channel reserve ("fee spike buffer"). A buffer of `2*feerate_per_kw` is
-    recommended to ensure predictability.
+    transaction, its remaining balance doesn't allow it to pay the fee to receive a
+    future additional non-dust HTLC while maintaining its channel reserve ("fee
+    spike buffer"). A buffer that expects the current `feerate_per_kw` to potentially
+    double is recommended to ensure predictability between implementations.
   - if it is _not responsible_ for paying the Bitcoin fee:
     - MUST NOT offer `amount_msat` if, once the remote node adds that HTLC to
     its commitment transaction, it cannot pay the fee for the updated local or