f some missing stuff

Author: TheBlueMatt

CHANGELOG.md

@@ -11,16 +11,21 @@
  * Rather than spawning a full OS thread, `lightning-background-processor` has
    a new `process_events_async` method which takes the place of a
    `BackgroundProcessor` for those using Rust's async (#1657).
+ * `ChannelManager::get_persistable_update_future` has been added to block on
+   a ChannelManager needing re-persistence in a Rust async environment (#1657).
  * The `Filter::register_output` return value has been removed, as it was
    very difficult to correctly implement (i.e., without blocking). Users
    previously using it should instead pass dependent transactions in via new
    `chain::Confirm::transactions_confirmed` calls (#1663).
  * `ChannelHandshakeConfig::their_channel_reserve_proportional_millionths` has
    been added to allow configuring counterparty reserve values (#1619).
+ * `KeysInterface::ecdh` has been added as an ECDH oracle (#1503, #1658).
  * The `rust-bitcoin` dependency has been updated 0.29 (#1658).
  * The `bitcoin_hashes` dependency has been updated 0.11 (#1677).
  * `ChannelManager::broadcast_node_announcement` has been moved to
    `PeerManager` (#1699).
+ * `channel_` and `node_announcement`s are now rebroadcast automatically to all
+   new peers which connect (#1699).
  * `{Init,Node}Features` sent to peers/broadcasted are now fetched via the
    various `*MessageHandler` traits, rather than hard-coded (#1701, #1688).
  * `Event::PaymentPathFailed::rejected_by_dest` has been renamed
@@ -52,8 +57,15 @@
 
 ## Backwards Compatibility
  * The new `current_time` argument to `PeerManager` constructors must be set to
-   a UNIX timestamp for upgraded nodes. Only new nodes may use a counter (#1699)
-XXX: fill this out
+   a UNIX timestamp for upgraded nodes, new nodes may use a counter (#1699).
+ * `Balance::CounterpartyRevokedOutputClaimable` will never be generated for
+   channels which were observed to go on-chain with LDK versions prior to
+   0.0.111 (#1495).
+ * `ChannelMonitor::get_counterparty_node_id` will return `None` for all
+   channels opened on a version of LDK prior to 0.0.110 (#1635).
+ * Setting `their_channel_reserve_proportional_millionths` to any value other
+   than the default will cause LDK versions prior to 0.0.104 to be unable to
+   read the serialized `ChannelManager` (#1619).
 
 ## Security
 0.0.111 fixes a denial-of-service vulnerability which is reachable from