core-lightning/onchaind
Rusty Russell 7895ff8fa8 onchaind: don't require an exact match for proposals.
The root cause of #1114 was that the restarted onchaind created a
different proposal to the one which had previously been mined:

	2018-03-01T09:41:08.884Z lightningd(1): lightning_onchaind-020d3d5995a973c878e3f6e5f59da54078304c537f981d7dcef73367ecbea0e90e chan #1: STATUS_FAIL_INTERNAL_ERROR: THEIR_UNILATERAL/OUR_HTLC spent with weird witness 3

After the previous patches which fixed the output address difference,
we could identify proposals by their outputs, but during the
transition (onchaind started with old buggy version, restarted now)
that wouldn't be right, so we match the inputs, discarding signatures
which will be different.  This works for all current cases.

Closes: #1114
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2018-03-07 18:55:51 +01:00
..
Makefile onchaind: keep billboard uptodate. 2018-02-23 18:02:00 +01:00
onchain_types.h onchain: implement penalty transaction. 2017-09-28 13:07:05 +09:30
onchain_wire.c Rename subdaemons, move them into top level. 2017-08-29 17:54:14 +02:00
onchain_wire.csv channel_states: fold all the ONCHAIND states into one. 2018-02-23 18:02:00 +01:00
onchain_wire.h Fix a-vs-an typos 2018-02-08 22:49:34 +01:00
onchain.c onchaind: don't require an exact match for proposals. 2018-03-07 18:55:51 +01:00