mirrors/lightning-bolts
1
0
Fork 0
mirror of https://github.com/lightning/bolts.git synced 2025-02-23 14:40:41 +01:00
Code Issues Projects Releases Wiki Activity

Delete obsolete reference to padding

Browse source
This commit is contained in:
EmelyanenkoK 2017-05-18 17:35:30 +04:00 • committed by Rusty Russell
parent 8b600e28ff
commit 032d55832d
1 changed files with 2 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
02-peer-protocol.md
View file

@ -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 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 Nodes MUST NOT broadcast old (revoked) commitment transactions; doing
so will allow the other node to seize all the funds. Nodes SHOULD NOT so will allow the other node to seize all the funds. Nodes SHOULD NOT