|
31 | 31 | to `lightning::util::config::ChannelConfig::max_dust_htlc_exposure_msat` per
|
32 | 32 | channel (#1009).
|
33 | 33 | * The interval on which
|
34 |
| - `lightning::ln::peer_handler::PeerManagertimer_tick_occurred` should be |
| 34 | + `lightning::ln::peer_handler::PeerManager::timer_tick_occurred` should be |
35 | 35 | called has been reduced to once every five seconds (#1035) and
|
36 | 36 | `lightning::ln::channelmanager::ChannelManager::timer_tick_occurred` should
|
37 | 37 | now be called on startup in addition to once per minute (#985).
|
|
66 | 66 | * Because
|
67 | 67 | `lightning::chain::keysinterface::KeysInterface::get_shutdown_scriptpubkey`
|
68 | 68 | has been updated to return a script instead of only a `PublicKey`,
|
69 |
| - `ChannelManager`s constructed with 0.0.100 and later versions will not be |
70 |
| - readable on previous versions. `ChannelManager`s created with 0.0.99 and |
71 |
| - prior versions will remain readable even after the a serialization roundtrip |
72 |
| - on 0.0.100, as long as no new channels are opened (#1019). |
| 69 | + `ChannelManager`s constructed with custom `KeysInterface` implementations on |
| 70 | + 0.0.100 and later versions will not be readable on previous versions. |
| 71 | + `ChannelManager`s created with 0.0.99 and prior versions will remain readable |
| 72 | + even after the a serialization roundtrip on 0.0.100, as long as no new |
| 73 | + channels are opened. Further, users using a |
| 74 | + `lightning::chain::keysinterface::KeysManager` as their `KeysInterface` will |
| 75 | + have `ChannelManager`s which are readable on prior versions as well (#1019). |
73 | 76 | * `ChannelMonitorUpdate`s created by 0.0.100 and later for channels when
|
74 | 77 | `lightning::util::config::ChannelConfig::commit_upfront_shutdown_pubkey` is
|
75 | 78 | not set may not be readable by versions prior to 0.0.100 (#1019).
|
|
0 commit comments