niftynei beec517910 df: persist our setting to disk, read back to dualopend at reinit ... It's not likely but possible that the node's settings will shift btw a start and an RBF; we persist the setting to the database so we don't lose it. Right now holding onto it forever is kind of extra but maybe we'll reuse the setting for splices? idk. Should this be a channel type??		2023-02-07 21:03:36 -06:00
..
test	df: persist our setting to disk, read back to dualopend at reinit	2023-02-07 21:03:36 -06:00
.gitignore	reorganize .gitignore entries across subdirs.	2021-05-18 09:43:50 +09:30
db.c	df: persist our setting to disk, read back to dualopend at reinit	2023-02-07 21:03:36 -06:00
db.h	database: pull out database code into a new module	2022-03-05 15:03:34 +10:30
invoices.c	delinvoice: allow desconly arg to only remove the description.	2022-03-29 10:04:16 +10:30
invoices.h	delinvoice: allow desconly arg to only remove the description.	2022-03-29 10:04:16 +10:30
Makefile	wallet: add dependency on lightningd/ headers.	2023-01-21 08:05:31 -06:00
reservation.c	fundpsbt: add option to filter out wrapped p2sh inputs	2023-02-04 15:31:16 +10:30
txfilter.c	all: no longer need to call htable_clear to free htable contents.	2023-01-12 11:44:10 +10:30
txfilter.h	common: use bitcoin_outpoint.	2021-10-15 12:09:36 +02:00
wallet.c	df: persist our setting to disk, read back to dualopend at reinit	2023-02-07 21:03:36 -06:00
wallet.h	fundpsbt: add option to filter out wrapped p2sh inputs	2023-02-04 15:31:16 +10:30
walletrpc.c	listtransactions: get rid of per-tx type annotations.	2023-01-30 15:15:41 -06:00
walletrpc.h	daemons: remove unused functions or make static.	2021-12-06 10:05:39 +10:30