niftynei 6771518e31 dualfund, reconnects: update dual-fund to use next-funding-id ... Here we conform to the specification, which requires that we handle next-funding-id in a specific way. Note that we were already sending it, but now we actually correctly handle its presence. Changelog-Changed: Spec: dual-funding now follows the next-funding-id rules.		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, reconnects: update dual-fund to use next-funding-id	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