core-lightning/lightningd/onchain_control.h

#ifndef LIGHTNING_LIGHTNINGD_ONCHAIN_CONTROL_H
#define LIGHTNING_LIGHTNINGD_ONCHAIN_CONTROL_H
#include "config.h"
#include <ccan/short_types/short_types.h>
#include <lightningd/lightningd.h>
#include <onchaind/onchaind_wiregen.h>

struct channel;
struct bitcoin_tx;
struct block;

enum watch_result onchaind_funding_spent(struct channel *channel,
					 const struct bitcoin_tx *tx,
					 u32 blockheight,
					 bool is_replay);

void onchaind_replay_channels(struct lightningd *ld);

#endif /* LIGHTNING_LIGHTNINGD_ONCHAIN_CONTROL_H */
lightningd/onchain_control: routines to control onchaind (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_ONCHAIN_CONTROL_H`
			`#define LIGHTNING_LIGHTNINGD_ONCHAIN_CONTROL_H`
			`#include "config.h"`
			`#include <ccan/short_types/short_types.h>`
onchaind: Replay stored channeltxs to restore onchaind state Signed-off-by: Christian Decker <decker.christian@gmail.com> 2018-04-17 15:31:30 +02:00			`#include <lightningd/lightningd.h>`
closingd: convert to new wire generation style. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> 2020-08-25 04:15:48 +02:00			`#include <onchaind/onchaind_wiregen.h>`
lightningd/onchain_control: routines to control onchaind (move from peer_control.c) Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> 2018-02-20 21:59:09 +01:00
			`struct channel;`
			`struct bitcoin_tx;`
			`struct block;`

onchaind: Add a level of indirection to txwatches and txowatches This will allow us in the next commit to store the transactions that triggered this event in the DB and thus allowing us to replay them later on. Signed-off-by: Christian Decker <decker.christian@gmail.com> 2018-04-16 13:20:45 +02:00			`enum watch_result onchaind_funding_spent(struct channel *channel,`
			`const struct bitcoin_tx *tx,`
coin moves: don't log coin moves in onchaind if we're replaying On node start we replay onchaind's transactions from the database/from our loaded htlc table. To keep things tidy, we shouldn't notify the ledger about these, so we wrap pretty much everything in a flag that tells us whether or not this is a replay. There's a very small corner case where dust transactions will get missed if the node crashes after the htlc has been added to the database but before we've successfully notified onchaind about it. Notably, most of the obtrusive updates to onchaind wrappings are due to the fact that we record dust (ignored outputs) before we receive confirmation of its confirmation. 2020-04-03 03:46:18 +02:00			`u32 blockheight,`
			`bool is_replay);`
lightningd/onchain_control: routines to control onchaind (move from peer_control.c) Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> 2018-02-20 21:59:09 +01:00
onchaind: Replay stored channeltxs to restore onchaind state Signed-off-by: Christian Decker <decker.christian@gmail.com> 2018-04-17 15:31:30 +02:00			`void onchaind_replay_channels(struct lightningd *ld);`

lightningd/onchain_control: routines to control onchaind (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_ONCHAIN_CONTROL_H */`