f ser compat and tweaks

Author: TheBlueMatt

CHANGELOG.md

@@ -16,6 +16,9 @@
    contains an `Option`al `NetGraphmsgHandler`. If provided as `Some`, relevant
    events will be processed by the `NetGraphMsgHandler` prior to normal event
    handling (#1043).
+ * `NetworkGraph` is now, itself, thread-safe. Accordingly, most functions now
+   take `&self` instead of `&mut self` and the graph data can be accessed
+   through `NetworkGraph.read_only()` (#1043).
  * The balances available on-chain to claim after a channel has been closed are
    now exposed via `ChannelMonitor::get_claimable_balances` and
    `ChainMonitor::get_claimable_balances`. The second can be used to get
@@ -37,7 +40,7 @@
    to be invalid, and requires millisatoshi values during construction (thus
    you must call `amount_milli_satoshis` instead of `amount_pico_btc`, #1057).
  * The `BaseSign` interface now includes two new hooks which provide additional
-   information about commigment transaction signatures and revocation secrets
+   information about commitment transaction signatures and revocation secrets
    provided by our counterparty, allowing additional verification (#1039).
  * The `BaseSign` interface now includes additional information for cooperative
    close transactions, making it easier for a signer to verify requests (#1064).
@@ -65,11 +68,16 @@
    handle the long hangs in Bitcoin Core when it syncs to disk (#1090).
 
 ## Serialization Compatibility
- * 
- * XXX There should at least be an entry for considerations around balances
- * XXX There should at least be an entry for payment error graph updates
- * XXX THere should at least be an entry for duplicate paymentfailed/sent for MPPs sent on old versions
- * XXX probably more.
+ * Payments which were initiated in versions prior to 0.0.101 may still
+   generate duplicate `PaymentSent` `Event`s or may have spurious values for
+   `Event::PaymentPathFailed::all_paths_failed` (#1053).
+ * The return values of `ChannelMonitor::get_claimable_balances` (and, thus,
+   `ChainMonitor::get_claimable_balances`) may be spurious for channels where
+   the spend of the funding transaction appeared on chain while running a
+   version prior to 0.0.101. `Balance` information should only be relied upon
+   for channels which were closed while running 0.0.101+ (#1034).
+ * Payments failed while running versions prior to 0.0.101 will never have a
+   `Some` for the `network_update` field (#1043).
 
 In total, this release features 68 files changed, 5046 insertions, 1887
 deletions in 84 commits from 12 authors, in alphabetical order: