niftynei c519c84ef8 df: handle funding_locked + tx_signatures messages out of order ... If we're doing an RBF, it's possible that the peer will send us a funding_locked, shutdown, or tx_signatures message. (We get tx_sigs out of order on a reconnect) This lets us gracefully handle a shutdown or funding_locked sent at any time (after first funding tx) as well.		2021-03-06 15:03:56 +10:30
..
common.c	df: use dev-env flagged upfront shutdown script	2021-01-10 13:44:04 +01:00
common.h	df: use dev-env flagged upfront shutdown script	2021-01-10 13:44:04 +01:00
dualopend.c	df: handle funding_locked + tx_signatures messages out of order	2021-03-06 15:03:56 +10:30
dualopend_wire.csv	rbf: consolidate failure paths, use "warnings"	2021-03-06 15:03:56 +10:30
dualopend_wiregen.c	rbf: consolidate failure paths, use "warnings"	2021-03-06 15:03:56 +10:30
dualopend_wiregen.h	rbf: consolidate failure paths, use "warnings"	2021-03-06 15:03:56 +10:30
Makefile	openingd: check upfront shutdown script.	2021-03-02 14:42:34 +10:30
openingd.c	common: support opt_shutdown_anysegwit checks (EXPERIMENTAL_FEATURES).	2021-03-02 14:42:34 +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