rgb-cln/onchaind
lisa neigut 9caf20f636 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-05-12 15:46:58 +09:30
..
test coin moves: don't log coin moves in onchaind if we're replaying 2020-05-12 15:46:58 +09:30
Makefile coin moves: record onchain movements after they've been resolved 2020-05-12 15:46:58 +09:30
onchain_types.h coin moves: record their attempted cheat (and our handling thereof) 2020-05-12 15:46:58 +09:30
onchain_wire.c onchaind: include htlc id in htlc_stub so we agree on what HTLC we're closing. 2018-10-23 16:55:35 +02:00
onchain_wire.csv coin moves: don't log coin moves in onchaind if we're replaying 2020-05-12 15:46:58 +09:30
onchain_wire.h onchaind: include htlc id in htlc_stub so we agree on what HTLC we're closing. 2018-10-23 16:55:35 +02:00
onchaind.c coin moves: don't log coin moves in onchaind if we're replaying 2020-05-12 15:46:58 +09:30