f include 3045

Author: TheBlueMatt

CHANGELOG.md

@@ -2,6 +2,11 @@
 
 ## API Updates
 
+ * To reduce risk of force-closures and improve HTLC reliability the default
+   dust exposure limit has been increased to
+   `MaxDustHTLCExposure::FeeRateMultiplier(10_000)`. Users with existing
+   channels might want to consider using
+   `ChannelManager::update_channel_config` to apply the new default (#3045).
  * `ChainMonitor::archive_fully_resolved_channel_monitors` is now provided to
    remove from memory `ChannelMonitor`s that have been fully resolved on-chain
    and are now not needed. It uses the new `Persist::archive_persisted_channel`
@@ -55,6 +60,9 @@
     LDK's persistence API was violated (#2974).
 
 ## Bug Fixes
+ * Excess fees on counterparty commitment transactions are now included in the
+   dust exposure calculation. This lines behavior up with some cases where
+   transaction fees can be burnt, making them effectively dust exposure (#3045).
  * `Future`s used as an `std::...::Future` could grow in size unbounded if it
    was never woken. For those not using async persistence and using the async
    `lightning-background-processor`, this could cause a memory leak in the