core-lightning/lightningd/closing_control.h

#ifndef LIGHTNING_LIGHTNINGD_CLOSING_CONTROL_H
#define LIGHTNING_LIGHTNINGD_CLOSING_CONTROL_H
#include "config.h"
#include <ccan/short_types/short_types.h>
#include <stdbool.h>

struct channel;
struct lightningd;
struct per_peer_state;

void resolve_close_command(struct lightningd *ld, struct channel *channel,
			   bool cooperative);

void peer_start_closingd(struct channel *channel,
			 struct per_peer_state *pps);

#endif /* LIGHTNING_LIGHTNINGD_CLOSING_CONTROL_H */
lightningd/closing_control: routines to control closingd (move from peer_control.c) Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> 2018-02-20 21:59:09 +01:00			`#ifndef LIGHTNING_LIGHTNINGD_CLOSING_CONTROL_H`
			`#define LIGHTNING_LIGHTNINGD_CLOSING_CONTROL_H`
			`#include "config.h"`
			`#include <ccan/short_types/short_types.h>`
lightningd/closing_control.c: move json_close here from peer_control.c They share some code, but not much: command_find_channel is made non-static. Rest is move-only. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> 2021-09-15 02:59:23 +02:00			`#include <stdbool.h>`
lightningd/closing_control: routines to control closingd (move from peer_control.c) Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> 2018-02-20 21:59:09 +01:00
lightningd: always pass closing connections through channeld. It handles all the cases of retransmission, and in the normal case retransmits shutdown and immediately returns for us to run closingd. This is actually far simpler and reduces code duplication. [ Includes fixup to stop warn_unused_result from Christian ] Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> Changelog-Fixed: Protocol: We could get stuck on signature exchange if we needed to retransmit the final revoke_and_ack. 2021-06-14 23:09:49 +02:00			`struct channel;`
lightningd/closing_control.c: move json_close here from peer_control.c They share some code, but not much: command_find_channel is made non-static. Rest is move-only. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> 2021-09-15 02:59:23 +02:00			`struct lightningd;`
common/per_per_state: generalize lightningd/peer_comm Part 1 Encapsulating the peer state was a win for lightningd; not surprisingly, it's even more of a win for the other daemons, especially as we want to add a little gossip information. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> 2019-06-03 20:11:25 +02:00			`struct per_peer_state;`
lightningd/closing_control: routines to control closingd (move from peer_control.c) Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> 2018-02-20 21:59:09 +01:00
lightningd/closing_control.c: move json_close here from peer_control.c They share some code, but not much: command_find_channel is made non-static. Rest is move-only. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> 2021-09-15 02:59:23 +02:00			`void resolve_close_command(struct lightningd ld, struct channel channel,`
			`bool cooperative);`

lightningd/closing_control: routines to control closingd (move from peer_control.c) Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> 2018-02-20 21:59:09 +01:00			`void peer_start_closingd(struct channel *channel,`
lightningd: always pass closing connections through channeld. It handles all the cases of retransmission, and in the normal case retransmits shutdown and immediately returns for us to run closingd. This is actually far simpler and reduces code duplication. [ Includes fixup to stop warn_unused_result from Christian ] Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> Changelog-Fixed: Protocol: We could get stuck on signature exchange if we needed to retransmit the final revoke_and_ack. 2021-06-14 23:09:49 +02:00			`struct per_peer_state *pps);`
lightningd/closing_control: routines to control closingd (move from peer_control.c) Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> 2018-02-20 21:59:09 +01:00
			`#endif /* LIGHTNING_LIGHTNINGD_CLOSING_CONTROL_H */`