pull down to refresh

Good notes, let me address them:
  • About the 1M channels problems when the mempool is congested, there should be no problem with modern implementations which use MPP. Anyway you have a good point, here is an additional config for that situation:
[onchain-congestion]
# if the onchain fee rate is high (>= 50 sat/vbyte) we increase the base fee to 20 sat
onchain.min_fee_rate = 50
base_fee_msat = 20_000
  • I used CL-BOSS when I had a CLN node. Thank you for informing that it is currently better updated. Do you know if now it does allow customization of the fee policy parameters?
  • I used the duplicate sqlite db sync when I had CLN, but I had to remove it because a failure in power supply causes out-of-sync, impeding that the node start, so it was useless in my case.
CLBOSS has five different "FeeModders" which collectively adjust channel fees. Some are configurable and some not. The most relevant one here is probably FeeModderByBalance which I've tried tweaking, but it doesn't have publicly accessible config parameters. We've been discussing in the calls ways to make it more responsive.
The power failure scenario is definitely a concern. I have a script to replace an outdated db, but I'm not sure such a feature from within the plugin would be appropriate. Maybe the plugin could document a generic pre-start db restore script though.
reply
Thank you for the info about FeeModders, I remember something about it, but I desisted because, as you say, it doesn't have accesible parameters. I hope this changes in the future. In general, I find CL-BOSS too much automatic and too little configurable. It's a pity because the idea is great.
Yes, I had a script too for the outdated db. I think everybody using that feature has it. But what is the point if it is not a reliable solution?
Because of these and many other things, I finally switched from CLN to LND. I'm happier now.
reply