1
0
mirror of https://github.com/lightning/bolts.git synced 2024-11-19 01:50:03 +01:00

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.
This commit is contained in:
Pierre-Marie Padiou 2019-06-05 16:23:13 +02:00 committed by GitHub
parent 309e86d471
commit e664b9e608
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

View File

@ -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`.