Matt Corallo d3af49e9f0 Limit inbound fee updates by dust exposure instead of our estimator ... Inbound fee udpates are rather broken in lightning as they can impact the non-fundee despite the funder paying the fee, but only in the dust exposure it places on the fundee. At least lnd is fairly aggressively high in their (non-anchor) fee estimation, running the risk of force-closure. Further, because we relied on a fee estimator we don't have full control over, we were assuming our users' fees are particularly conservative, and thus were at a lot of risk to force-closures. This converts our fee limiting to use an absurd upper bound, focusing on whether we are over-exposed to in-flight dust when we receive an update_fee.		2021-08-13 21:54:50 +00:00
..
chain	Add standard derives for ConfirmationTarget	2021-08-10 22:26:13 +00:00
ln	Limit inbound fee updates by dust exposure instead of our estimator	2021-08-13 21:54:50 +00:00
routing	Rename no_std feature to no-std	2021-08-03 18:53:33 +02:00
util	Merge pull request #1009 from ariard/2021-07-add-forward-dust-limit	2021-08-10 22:11:18 +00:00
lib.rs	Rename no_std feature to no-std	2021-08-03 18:53:33 +02:00
sync.rs	Implement dummy Mutex, Condvar and RwLock	2021-07-20 20:59:18 +02:00