Files
lightning/daemon
Rusty Russell 4319f3ac70 peer: explicitly store the previous revocation hash when sending new update.
We want to stop keeping old commitment information (except the minimal
txid to commitment-number mapping).  One place we currently use it is
after sending a commitment signature, and before we've received the
revocation for the old commitment.  For this duration, there are two
valid commitment transactions.

So we store "their_prev_revocation_hash" explicitly for this duration.

Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2016-08-18 14:23:46 +09:30
..
2016-01-22 06:41:47 +10:30
2016-07-20 11:51:28 +09:30
2016-07-01 12:00:17 +09:30
2016-01-22 06:45:28 +10:30
2016-08-18 14:23:46 +09:30
2016-08-18 14:23:46 +09:30
2016-01-22 06:41:49 +10:30
2016-08-18 14:23:45 +09:30
2016-08-18 14:23:45 +09:30
2016-08-18 14:23:45 +09:30
2016-05-26 15:25:24 +09:30
2016-05-26 15:25:24 +09:30
2016-07-01 12:00:17 +09:30
2016-07-01 12:00:17 +09:30
2016-08-17 14:46:42 +09:30
2016-08-17 14:46:42 +09:30
2016-05-10 06:28:17 +09:30
2016-05-10 06:28:17 +09:30
2016-07-01 12:00:17 +09:30
2016-07-01 11:59:15 +09:30
2016-07-01 11:59:15 +09:30
2016-07-01 12:00:17 +09:30
2016-07-01 12:00:17 +09:30
2016-07-01 12:00:17 +09:30
2016-08-18 14:23:46 +09:30
2016-08-18 14:23:46 +09:30
2016-05-10 06:26:09 +09:30
2016-05-10 06:26:09 +09:30