Rusty Russell e96eb07ef4 lightningd: test that hsm_secret is as expected, at startup. ... If you get the wrong hsm_secret, your node_id will change, and peers won't know who you are, bitcoind will reject your transaction signatures, and other madness. Catch this as soon as it happens, by storing our node_id in the db. Suggested-by: @cdecker, @fiatjaf Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> Changelog-Changed: Config: `lightningd` will refuse to start with the wrong node_id (i.e. hsm_secret changes).		2022-07-20 19:28:33 +09:30
..
Makefile	common: clean up json routine locations.	2022-07-15 12:24:00 -05:00
run-find_my_abspath.c	lightningd: test that hsm_secret is as expected, at startup.	2022-07-20 19:28:33 +09:30
run-invoice-select-inchan.c	lightningd: drive all reconnections out of disconnections.	2022-07-18 20:50:04 -05:00
run-jsonrpc.c	lightningd/json.h: remove.	2022-07-15 12:24:00 -05:00
run-log-pruning.c	lightningd: don't explicitly tell connectd to disconnect, have it do it on sending error/warning.	2022-07-18 20:50:04 -05:00
run-shuffle_fds.c	common: clean up json routine locations.	2022-07-15 12:24:00 -05:00