lightning

107 Tags

38 MiB

Tree: 254ee8a5d3

Author	SHA1	Message	Date
Rusty Russell	207eeae1f7	lightningd: explictly split htlc_in and htlc_out. They share some fields, but they're basically different, and it's clearest to treat them differently in most places. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>	8 years ago
Rusty Russell	61906ea415	channeld: don't keep shachain. The master daemon is the one which stores it, have it do the check. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>	8 years ago
Rusty Russell	4a161b710d	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>	8 years ago
Rusty Russell	7c9b66e67f	lightningd: peer_htlcs.c Move HTLC handling out of peer_control.c. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>	8 years ago