mirror of
https://github.com/lightningdevkit/rust-lightning.git
synced 2025-02-27 00:06:34 +01:00
75c058670c
Upon creating a channel monitor, it is provided with the initial counterparty commitment transaction info directly before the very first time it is persisted. Because of this, the very first counterparty commitment is not seen as an update in the persistence pipeline, and so our previous changes to the monitor and updates cannot be used to reconstruct this commitment. To be able to expose the counterparty's transaction for the very first commitment, we add a thin wrapper around `provide_latest_counterparty_commitment_tx`, that stores the necessary data needed to reconstruct the initial commitment transaction in the monitor. |
||
|---|---|---|
| .. | ||
| chan_utils.rs | ||
| chanmon_update_fail_tests.rs | ||
| channel.rs | ||
| channelmanager.rs | ||
| features.rs | ||
| functional_test_utils.rs | ||
| functional_tests.rs | ||
| inbound_payment.rs | ||
| mod.rs | ||
| monitor_tests.rs | ||
| msgs.rs | ||
| onion_route_tests.rs | ||
| onion_utils.rs | ||
| outbound_payment.rs | ||
| payment_tests.rs | ||
| peer_channel_encryptor.rs | ||
| peer_handler.rs | ||
| priv_short_conf_tests.rs | ||
| reload_tests.rs | ||
| reorg_tests.rs | ||
| script.rs | ||
| shutdown_tests.rs | ||
| wire.rs | ||