pull down to refresh
0 sats \ 0 replies \ @javier OP 16h \ parent \ on: Ultimate guide to LN routing and fee management. bitcoin
As I said, losing is imposible because it is a discount. But if you don't believe me, let Lighting Labs tell you so:
https://docs.lightning.engineering/lightning-network-tools/lnd/inbound-channel-fees
Fee policy means outbound fee policy, yes.
Inbound policies are a thing available in LND only, I think, but there is a BLIP: https://github.com/lightning/blips/pull/18
Other implementations should enable this, but you know CLN, it is always the last one and usually it comes late. Another reason not to choose CLN added to the long list.
For setting inbound fees graphically I know of LNDg in their advanced settings tab, which is also a good rebalancer and has a good interface (only for desktop).
Sure, the fee is the outbound fee, which means the fee you charge for going out. So in your example, A pays 5 sats to you. B doesn't pay anything to you. But in addition to pay you, A will pay to B whatever B has as outbound fee (you can't control this).
Another thing is the inbound fee which is always negative or 0, and it is a discount. So if you put an inbound fee of -5, A will pay 0, because A is the inbound and B is the outbound which you put an outbound fee of 5, so the discount applies: 5-5=0. Do not confuse this with the outbound of A which is 1. Remember, outbound and inbound fees are different, they are not the same parameter, each channel has both fees, both inbound and outbound.
Any more questions I will happily answer.
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.
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.
Ok, so just another speculative question, answer if you want: so the final objective of all of this is to enable proper Citrea operation, which will imply bringing Defi and nUSD (similar to Tether) directly to the Bitcoin blockchain without the need of a sidechain?
Is there any estimation on how much would this affect fees for the average user, considering external projects (like Citrea) using it? Any possibility that this could saturate the mempool and boost fees beyond reasonable?
I have never used Start9 so I don't know. A quick search doesn't reveal anything relevant. I know that umbrel has charge-lnd, so Start9 should have it, right? It would be a good idea to ask support, or in their forum.
That's why I ended my CLN node last year and started a new LND.
I used CLBOSS, and it is updated for bug fixes only. It has limited capabilities in comparison with all the spectrum of tools available for LND.
I'm sorry to say.