Matt Corallo 03439ec99f Automatically update fees on outbound channels as fees change ... Previously we'd been expecting to implement anchor outputs before shipping 0.1, thus reworking our channel fee update process entirely and leaving it as a future task. However, due to the difficulty of working with on-chain anchor pools, we are now likely to ship 0.1 without requiring anchor outputs. In either case, there isn't a lot of reason to require that users call an explicit "prevailing feerates have changed" function now that we have a timer method which is called regularly. Further, we really should be the ones deciding on the channel feerate in terms of the users' FeeEstimator, instead of requiring users implement a second fee-providing interface by calling an update_fee method. Finally, there is no reason for an update_fee method to be channel-specific, as we should be updating all (outbound) channel fees at once. Thus, we move the update_fee handling to the background, calling it on the regular 1-minute timer. We also update the regular 1-minute timer to fire on startup as well as every minute to ensure we get fee updates even on mobile clients that are rarely, if ever, open for more than one minute.		2021-08-13 21:54:50 +00:00
..
src	Automatically update fees on outbound channels as fees change	2021-08-13 21:54:50 +00:00
Cargo.toml	Bump dependencies to bitcoin 0.27 and bech32 0.8	2021-07-31 18:29:07 +00:00