niftynei b2d2796aad dualfund, tx-abort: only check for abort state if we're sending ... In the case where you're echoing back a tx-abort, just let it through. Not doing this causes problems in the case where your node has forgotten about an in-progress open. This fixes the following problem: - you send a tx-abort (even tho you have marked tx-sigs as received) - peer echos it back (we echo back tx-aborts always) - you throw an error because you're already in a tx-abort unallowed state In this commit, we allow for echos to come thru no matter our current state and this fixes things/makes them work as expected.		2023-11-02 19:32:05 +10:30
..
common.c	openingd: remove #if DEVELOPER in favor of runtime flag.	2023-09-21 20:08:24 +09:30
common.h	openingd: remove #if DEVELOPER in favor of runtime flag.	2023-09-21 20:08:24 +09:30
dualopend.c	dualfund, tx-abort: only check for abort state if we're sending	2023-11-02 19:32:05 +10:30
dualopend_wire.csv	dualfund: report on whether or not we've gotten commitments	2023-11-02 19:32:05 +10:30
Makefile	tx_roles: allow to be serialized btw processes	2023-02-07 21:03:36 -06:00
openingd.c	hsmd: name the hsmd_ready_channel to hsmd_setup_channel	2023-10-23 16:04:30 +10:30
openingd_wire.csv	openingd: Reject zeroconf if the peer is not allowed	2023-08-18 20:30:03 +09:30