niftynei 382264e207 dualopend: don't use final channel_id for accepter_start2 ...

The other side doesn't know it until *after* it parses this msg.  We
add a quick hack to still allow old nodes to work (for now!).

This also fixes a bug (spotted by @niftynei) where any errors we sent
before accepter_start2 would have the new (unknowable!) channel_id
rather than the temp one.

Authored-by: Rusty Russell <rusty@rustcorp.com.au>

2021-05-03 11:06:10 +09:30

..

common.c

doc: remove suffix for included-in-master BOLTs.

2021-04-07 14:34:39 +09:30

common.h

df: use dev-env flagged upfront shutdown script

2021-01-10 13:44:04 +01:00

dualopend_wire.csv

df-spec: consolidate dual-funding patches, update feerate protocol

2021-03-09 14:55:05 +10:30

dualopend_wiregen.c

df-spec: consolidate dual-funding patches, update feerate protocol

2021-03-09 14:55:05 +10:30

dualopend_wiregen.h

df-spec: consolidate dual-funding patches, update feerate protocol

2021-03-09 14:55:05 +10:30

dualopend.c

dualopend: don't use final channel_id for accepter_start2

2021-05-03 11:06:10 +09:30

Makefile

dual-funding: convert to runtime flag, --experimental-dual-fund

2021-03-25 20:05:11 +10:30

openingd_wire.csv

openingd: convert wire to new scheme.

2020-08-25 12:53:13 +09:30

openingd_wiregen.c

tools/generate-wire.py: include digits in #ifndef idempotent header.

2021-01-13 14:45:36 +01:00

openingd_wiregen.h

tools/generate-wire.py: include digits in #ifndef idempotent header.

2021-01-13 14:45:36 +01:00

openingd.c

plugin: Do not send the internal framed message over the wire

2021-03-09 14:39:22 +10:30