Matt Corallo 496eb4526b Create SpendableOutputs events no matter the chain::Confirm order ... We had a user who pointed out that we weren't creating `SpendableOutputs` events when we should have been after they called `ChannelMonitor::best_block_updated` with a block well after a CSV locktime and then called `ChannelMonitor::transactions_confirmed` with the transaction which we should have been spending (with a block height/hash a ways in the past). This was due to `ChannelMonitor::transactions_confirmed` only calling `ChannelMonitor::block_confirmed` with the height at which the transactions were confirmed, resulting in all checks being done against that, not the current height. Further, in the same scenario, we also would not fail-back and HTLC where the HTLC-Timeout transaction was confirmed more than ANTI_REORG_DELAY blocks ago. To address this, we use the best block height for confirmation threshold checks in `ChannelMonitor::block_confirmed` and pass both the confirmation and current heights through to `OnchainTx::update_claims_view`, using each as appropriate. Fixes #962.		2021-07-02 17:16:12 +00:00
..
src	Create SpendableOutputs events no matter the chain::Confirm order	2021-07-02 17:16:12 +00:00
Cargo.toml	Use hashbrown replacements for std equivalents	2021-06-18 21:54:21 +00:00