aljaz/lightning
1
0
Fork 0
mirror of https://github.com/aljazceru/lightning.git synced 2026-01-03 22:34:21 +01:00
Code Issues Packages Projects Releases Wiki Activity

BOLT: Update text to latest commit.

Browse Source 
This brings us up to 955e874acc535ab2c74c1cf0eab61896ea4224ff in
https://github.com/lightningnetwork/lightning-rfc

This doesn't actually change anything; the only actual change is held back
for the next commit.

Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
This commit is contained in:
Rusty Russell
2017-08-22 13:15:41 +09:30
committed by Christian Decker
parent 1ffb9f07c1
commit fea412dd94
5 changed files with 34 additions and 29 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
lightningd/channel/channel.c
View File

@@ -1545,7 +1545,7 @@ again:
/* BOLT #2:
*
* If `next_remote_revocation_number` is equal to the commitment
* number of the last `revoke_and_ack` the receiving node has sent, it
* number of the last `revoke_and_ack` the receiving node has sent and the receiving node has not already received a `closing_signed`, it
* MUST re-send the `revoke_and_ack`, otherwise if
* `next_remote_revocation_number` is not equal to one greater than
* the commitment number of the last `revoke_and_ack` the receiving
@@ -1614,9 +1614,11 @@ again:
/* BOLT #2:
*
* On reconnection if the node has sent a previous `shutdown` it MUST
* retransmit it
* On reconnection if the node has sent a previous `closing_signed` it
* MUST send another `closing_signed`, otherwise if the node has sent
* a previous `shutdown` it MUST retransmit it.
*/
/* If we had sent `closing_signed`, we'd be in closingd. */
maybe_send_shutdown(peer);
/* Corner case: we didn't send shutdown before because update_add_htlc