When there is a channel closure and the fees are low LND increases the fee. Is there any chance to change when the fees should be increase? or how they should be increased?
Give an example.
Most of the time, I set the limit on the fee, and there is no increase when I close a channel.
You can try this GitHub - accumulator/charge-lnd: charge-lnd is a simple policy based fee manager for LND. With this tool you can set fees to autobalance, recover channel open costs, use on-chain fees as reference, use channel activity to determine fees or just use static fees. to manage your Lightning node fees. Have it run on a schedule every 1-2 hours You could start with a configuration like the below, but you should study and make corrections according to your needs. I expect you have some basic Linux knowledge how to set up docker containers and cron jobs. If not, do not try it.
[default]
# 'default' is special, it is used if no other policy matches a channel
strategy = static
base_fee_msat = 0
fee_ppm = 512
inbound_base_fee_msat = 0
inbound_fee_ppm = 0
min_fee_ppm_delta=20
[mydefaults]
# no strategy, so this only sets some defaults
base_fee_msat = 0
min_fee_ppm_delta = 0
### Set MIN HTLC for all channels to 100sat###
min_htlc_msat = 100000
[lost-onchain-sync]
# The fact that lnd was not synchronized with the chain for more than 5 minutes
# was an indicator of a severe problem in the past.
onchain.synced_to_chain = false
base_fee_msat = 210_000
fee_ppm = 210_000
[expensive]
# match channels where the peer node has set a high (>=8_000 ppm) fee rate
# and set the same fee rate on our side (strategy=match_peer)
chan.min_fee_ppm = 8000
strategy = match_peer
[leafnode]
# charge non-routing (private=true) peers a bit more for our service
chan.private = true
strategy = static
fee_ppm = 1000
[encourage-routing]
# 'autobalance' (lower fees so using outbound is more attractive)
chan.min_ratio = 0.98
inbound_base_fee_msat = 0
inbound_fee_ppm = 0
strategy = static
base_fee_msat = 0
fee_ppm = 64
# If channel capacity is +98% set full MAX HTLC
max_htlc_msat_ratio = 1
[discourage-routing]
# 'autobalance' (higher fees so using outbound is less attractive)
chan.max_ratio = 0.3
chan.min_ratio = 0.1
strategy = proportional
inbound_base_fee_msat = -64
inbound_fee_ppm = -32
min_fee_ppm = 384
max_fee_ppm = 1024
base_fee_msat = 1_000
# Signal low liquidity by setting lower HTLC
max_htlc_msat_ratio = 0.1
[all-liquidity-is-theirs]
chan.max_ratio = 0.00
inbound_base_fee_msat = -128
inbound_fee_ppm = -128
strategy = static
base_fee_msat = 1_000
fee_ppm = 9999
# Signal low liquidity by setting low HTLC
max_htlc_msat_ratio = 0.001
[discourage-routing-extreme]
chan.max_ratio = 0.1
inbound_base_fee_msat = -128
inbound_fee_ppm = -100
strategy = proportional
min_fee_ppm = 1024
max_fee_ppm = 2048
base_fee_msat = 1_000
# Signal low liquidity by setting low HTLC
max_htlc_msat_ratio = 0.01
[proportional]
# 'proportional' can also be used to auto balance (lower fee rate when low remote balance & higher rate when higher remote balance)
chan.min_ratio = 0.3
chan.max_ratio = 0.98
strategy = proportional
min_fee_ppm = 64
# 20% excess, so for a max of 128, it’s calculated 128/(1-0.20)=160
max_fee_ppm = 384
inbound_base_fee_msat = 0
inbound_fee_ppm = 0
base_fee_msat = 0
min_fee_ppm_delta=16
# Set MAX HTLC to 60% of channel capacity
max_htlc_msat_ratio = 0.6
How is this different than Ride The Lightning and ThunderHub Apps with LDN Node?
charge-lnd runs on auto-pilot and continuously arrange the fees according to the circumstances, based on pre-defined rules. As far as I know, in Ride the Lightning and ThunderHub the user needs to change the fees manually. If automation is not needed, then both RTL and TH are great.
I prefer LNDg but I hear good things about charge-lnd.
I also like LNDg, although it seemed a bit heavy to me. It may run better on faster hardware. It’s also more convenient since it’s already in Umbrel store 
1 Like