4 commits

Author	SHA1	Message	Date
Rusty Russell	3f65f0f000	lightningd: fix up malformed onion handling. ... In the case where we can't decrypt the onion, we can't fail it in the normal way (which is encrypted using the onion shared secret), we need to respond with a update_fail_malformed_htlc message. Moreover, we need to remember this for persistence. This means that we really have three conclusions for an HTLC: fulfilled, failed, malformed. Fix up the logic everywhere which assumed failed or fulfilled. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>	2017-06-23 09:29:42 +09:30
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>	2017-06-23 09:29:42 +09:30
Rusty Russell	798c4b73c4	lightningd/htlc_end: fix key for stricter compiler. ... We *should* split the struct into key and data, rather than only comparing the key parts in the htlc_end_eq function. But meanwhile, this fixes the code. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>	2017-04-02 09:36:29 +09:30
Rusty Russell	826fb0c2dc	lightningd: track HTLC ends. ... This lets us link HTLCs from one peer to another; but for the moment it simply means we can adjust balance when an HTLC is fulfilled. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>	2017-04-01 23:59:46 +10:30