niftynei 89f6fd27e3 dual-fund: have accepter send their commitment sigs asap ... Originally the accepter waited for the peer to send us their commitment sigs before we send ours; this changes things so that the accepter sends their commitment sigs ASAP. This test fails: when cln is not the channel initiator, it waits for the other node to send commit_sig before sending its own commit_sig. There is no reason to do that, both nodes should send commit_sig immediately after exchanging tx_complete? Otherwise it's a missed opportunity to finalize the channel creation on reconnection, because in that case cln hasn't saved the channel and fails it on reconnection. Reported-By: @t-bast		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_wire.csv	dualfund: report on whether or not we've gotten commitments	2023-11-02 19:32:05 +10:30
dualopend.c	dual-fund: have accepter send their commitment sigs asap	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_wire.csv	openingd: Reject zeroconf if the peer is not allowed	2023-08-18 20:30:03 +09:30
openingd.c	hsmd: name the hsmd_ready_channel to hsmd_setup_channel	2023-10-23 16:04:30 +10:30