pull down to refresh

I think the only way to truly understand LNDg is to looking at the source code, it's python so it's almost like english pseudocode.
LNDg is a natural extension of what you want to automatize if you manage your node, so most of the functionality is a re-flexion of that.
Do you want to maintain a balance channel? maybe you want to answer these questions:
  • What balance? 50/50, 20/70
  • From what place do you want to get the "liquidity"? any other channel? an specific set of inbound channels?
  • When you want to start the "re-balance"? When you want to stop?
  • Do you want to fill the balance with only a few invoices? many?
  • How often do you want to try create those invoices?
For all that questions LNDg has a configuration, and those are only related with re-balance a channel.
It's too much info, for me... the best thing to do is to use the "water pipes" analogy and just focus in manage the min/max htlc, set a price you are comfortable and just let the water flow.
If you are in the path of learning, just start to do things manually (less than 20channels) and write what "task" you are doing, then try to automatize that, probably with 10% of the functionality of LNDg is enough.
PD: LNDg is network intensive... bad for Tor only nodes.
Thanks for the information. That's a lot of what I was looking for. Regarding it being network intensive, would those same issues exist with a hybrid node? In fact more generally, can you explain hybrid nodes? I know you can connect with both clearnet and Tor peers running a hybrid node. I do that, with tailscale.
reply
So, in your case (tailscale) as far I know is a VPN (tunnel), you have less hops but it's not the same as a clearnet only node without any hop in the middle.
Your node => Tor => Tor => Tor => Other node Your node => VPN => Other node Your node => Other node
In a competition to "find" the best path between two nodes, less (network) hops are good.
reply
Understood. Thanks.
reply