From ad3ed9d9fac470a403c35f077d7bdd51f0712253 Mon Sep 17 00:00:00 2001 From: Pierre-Marie Padiou Date: Wed, 27 Oct 2021 17:16:24 +0200 Subject: [PATCH] Clarify and relax requirements on `channel_reestablish` The peer that is using an outdated commitment must not fail the channel itself, rather it should request the other peer to fail the channel. --- 02-peer-protocol.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/02-peer-protocol.md b/02-peer-protocol.md index 28a32ff45..ddff53e3b 100644 --- a/02-peer-protocol.md +++ b/02-peer-protocol.md @@ -1381,7 +1381,7 @@ A node: `your_last_per_commitment_secret` is correct for that `next_revocation_number` minus 1: - MUST NOT broadcast its commitment transaction. - - SHOULD fail the channel. + - SHOULD send an `error` to request the peer to fail the channel. - otherwise: - if `your_last_per_commitment_secret` does not match the expected values: - SHOULD fail the channel. @@ -1390,7 +1390,7 @@ A node: `your_last_per_commitment_secret` is correct for that `next_revocation_number` minus 1: - MUST NOT broadcast its commitment transaction. - - SHOULD fail the channel. + - SHOULD send an `error` to request the peer to fail the channel. - SHOULD store `my_current_per_commitment_point` to retrieve funds should the sending node broadcast its commitment transaction on-chain. - otherwise (`your_last_per_commitment_secret` or `my_current_per_commitment_point`