Description
If the number of opened channels is too high and our fee-bumping reserves are too low, we should reject new inbound channels to avoid a situation where we cannot cover high feerates at current level of network mempools congestion. This type of mechanism is already implemented by LND.
#2089’s CoinSelectionSource
could return the level of fee-bumping reserves currently available (e.g get_available_utxos
). This method could be called by ChannelManager::timer_tick_occurred
and in function refuse new channels in ``do_accept_inbound_channels`.
Sounds a follow-up of #2089.
(merged from #2327)
If the numbers of pending HTLCs is too high and our fee-bumping reserves are too low, we should reject new HTLC forwarding request to avoid a situation where we cannot cover high feerates at current level of network mempools congestion. This type of mechanism is not implemented by any Lightning implementation, afaik.
This type of checks could be introduced in the same code path where we're checking other BOLT4 checks in decode_update_add_htlc_onion() or offloaded to the LDK user if we can have a generic HTLC interception interface.