From 945051e4b023a3d29d2f667a801ee25d4f7b3c14 Mon Sep 17 00:00:00 2001
From: Orfeas Stefanos Thyfronitis Litos <o.thyfronitis@ed.ac.uk>
Date: Tue, 15 Jan 2019 16:23:51 +0000
Subject: [PATCH] Clarify behavior of id field in update_add_htlc

Clarify that the id value is not reset after an update is complete
---
 02-peer-protocol.md | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/02-peer-protocol.md b/02-peer-protocol.md
index 3bd0dad..f8e86f4 100644
--- a/02-peer-protocol.md
+++ b/02-peer-protocol.md
@@ -794,6 +794,9 @@ Fees") while maintaining its channel reserve.
     - MUST set `id` to 0.
   - MUST increase the value of `id` by 1 for each successive offer.
 
+`id` MUST NOT be reset to 0 after the update is complete (i.e. after `revoke_and_ack` has
+been received). It MUST continue incrementing instead.
+
 A receiving node:
   - receiving an `amount_msat` equal to 0, OR less than its own `htlc_minimum_msat`:
     - SHOULD fail the channel.