lnd/lntest/itest
Joost Jager 67e40d4433
htlcswitch: always assume an onion error for malformed htlc failures
Previously a temporary channel failure was returning for unexpected
malformed htlc failures. This is not what we want to communicate to the
sender, because the sender may apply a penalty to us only.

Returning the temporary channel failure is especially problematic if we
ourselves are the sender and the malformed htlc failure comes from our
direct peer. When interpretating the failure, we aren't able to
distinguish anymore between our channel not having enough balance and
our peer sending an unexpected failure back.
2019-08-17 10:24:05 +02:00
..
lnd_multi-hop_htlc_local_chain_claim_test.go itest+routing: updating tests to account for BlockPadding 2019-07-23 21:03:30 -04:00
lnd_multi-hop_htlc_receiver_chain_claim_test.go itest+routing: updating tests to account for BlockPadding 2019-07-23 21:03:30 -04:00
lnd_multi-hop_htlc_remote_chain_claim_test.go itest+routing: updating tests to account for BlockPadding 2019-07-23 21:03:30 -04:00
lnd_test.go htlcswitch: always assume an onion error for malformed htlc failures 2019-08-17 10:24:05 +02:00
onchain.go lntest: add CPFP integration test 2019-06-11 15:06:41 -07:00