core-lightning/lightningd/peer_htlcs.h

/* All about the HTLCs/commitment transactions for a particular peer. */
#ifndef LIGHTNING_LIGHTNINGD_PEER_HTLCS_H
#define LIGHTNING_LIGHTNINGD_PEER_HTLCS_H
#include "config.h"
#include <ccan/short_types/short_types.h>

int peer_sending_commitsig(struct peer *peer, const u8 *msg);
int peer_got_commitsig(struct peer *peer, const u8 *msg);
int peer_got_revoke(struct peer *peer, const u8 *msg);

#endif /* LIGHTNING_LIGHTNINGD_PEER_HTLCS_H */
lightningd: peer_htlcs.c Move HTLC handling out of peer_control.c. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> 2017-06-20 07:45:03 +02:00			`/* All about the HTLCs/commitment transactions for a particular peer. */`
			`#ifndef LIGHTNING_LIGHTNINGD_PEER_HTLCS_H`
			`#define LIGHTNING_LIGHTNINGD_PEER_HTLCS_H`
			`#include "config.h"`
			`#include <ccan/short_types/short_types.h>`

channeld: pass htlcs to master daemon in batches. When adding their HTLCs, it needs all the information. When failing, it needs the id as key and the failure reason. When fulfilling, it needs the id and payment preimage. It also needs to know when we have received an revoke_and_ack or a commitment_signed, to place in the database. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> 2017-06-20 07:50:03 +02:00			`int peer_sending_commitsig(struct peer peer, const u8 msg);`
			`int peer_got_commitsig(struct peer peer, const u8 msg);`
			`int peer_got_revoke(struct peer peer, const u8 msg);`
lightningd: peer_htlcs.c Move HTLC handling out of peer_control.c. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> 2017-06-20 07:45:03 +02:00
			`#endif /* LIGHTNING_LIGHTNINGD_PEER_HTLCS_H */`