From e664b9e608b9d69de4dd866d98e2b2bb4bcc0346 Mon Sep 17 00:00:00 2001
From: Pierre-Marie Padiou <pm47@users.noreply.github.com>
Date: Wed, 5 Jun 2019 16:23:13 +0200
Subject: [PATCH] BOLT 2: Should not send identical fee changes

See https://github.com/ElementsProject/lightning/issues/2701 for context.

I went with *MUST NOT* to be consistent with:

> A sending node:
>  - MUST NOT send a `commitment_signed` message that does not include any
updates.
---
 02-peer-protocol.md | 1 +
 1 file changed, 1 insertion(+)

diff --git a/02-peer-protocol.md b/02-peer-protocol.md
index 775426e..f386525 100644
--- a/02-peer-protocol.md
+++ b/02-peer-protocol.md
@@ -1049,6 +1049,7 @@ given in [BOLT #3](03-transactions.md#fee-calculation).
 The node _responsible_ for paying the Bitcoin fee:
   - SHOULD send `update_fee` to ensure the current fee rate is sufficient (by a
       significant margin) for timely processing of the commitment transaction.
+  - MUST NOT send identical consecutive `update_fee`s.
 
 The node _not responsible_ for paying the Bitcoin fee:
   - MUST NOT send `update_fee`.