Matt Corallo 0f6b0004c4 Fix two bugs which access the wrong peer's htlc_minimum_msat value ... * Channel::get_counterparty_htlc_minimum_msat() returned holder_htlc_minimum_msat, which was obviously incorrect. * ChannelManager::get_channel_update set htlc_minimum_msat to Channel::get_holder_htlc_minimum_msat(), but the spec explicitly states we "MUST set htlc_minimum_msat to the minimum HTLC value (in millisatoshi) that the channel peer will accept." This makes sense because the reason we're rejecting the HTLC is because our counterparty's HTLC minimum value is too small for us to send to them, our own HTLC minimum value plays no role. Further, our router already expects this - looking at the same directional channel info as it does fees. Finally, we add a test in the existing onion router test cases which fails if either of the above is incorrect (the second issue discovered in the process of writing the test).		2020-09-16 11:12:51 -04:00
..
src	Fix two bugs which access the wrong peer's htlc_minimum_msat value	2020-09-16 11:12:51 -04:00
Cargo.toml	Update to latest upstream rust-bitcoin	2020-09-10 16:20:01 -04:00