From 032d55832d99f30de32e6e8ce44ad7f8f2393c1a Mon Sep 17 00:00:00 2001 From: EmelyanenkoK Date: Thu, 18 May 2017 17:35:30 +0400 Subject: [PATCH] Delete obsolete reference to `padding` --- 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 6c369a6..6c6e720 100644 --- a/02-peer-protocol.md +++ b/02-peer-protocol.md @@ -814,9 +814,9 @@ The description of key derivation is in [BOLT #3](03-transactions.md#key-derivat A sending node MUST set `per_commitment_secret` to the secret used to generate keys for the -previous commitment transaction, MUST set `next_per_commitment_point` to the values for its next commitment transaction, and MUST set `padding` to all zeroes. +previous commitment transaction, MUST set `next_per_commitment_point` to the values for its next commitment transaction. -A receiving node MUST check that `per_commitment_secret` generates the previous `per_commitment_point`, and MUST fail if it does not. A receiving node MUST ignore the value of `padding`. A receiving node MAY fail if the `per_commitment_secret` was not generated by the protocol in [BOLT #3](03-transactions.md#per-commitment-secret-requirements). +A receiving node MUST check that `per_commitment_secret` generates the previous `per_commitment_point`, and MUST fail if it does not. A receiving node MAY fail if the `per_commitment_secret` was not generated by the protocol in [BOLT #3](03-transactions.md#per-commitment-secret-requirements). Nodes MUST NOT broadcast old (revoked) commitment transactions; doing so will allow the other node to seize all the funds. Nodes SHOULD NOT