counterweight/chatochi_notes
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Notes on charge-lnd

Browse source
This commit is contained in:
pablo 2022-01-20 12:13:16 +01:00
parent 7a525d7cec
commit c10832cf52
1 changed files with 33 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

32
lightning_node_management.md
View file

@ -258,3 +258,35 @@ it said "Check out my node, Baystar!", together with a public key. Lovely,
this guy is just sending random spam messages to people to get some attention. this guy is just sending random spam messages to people to get some attention.
The lightning network keeps on feeling like the wild wild west, where funny The lightning network keeps on feeling like the wild wild west, where funny
things just happen out of the blue. things just happen out of the blue.
## A professional knows its price
As I am beginning and trying things out, I haven't paid much attention to the
fees in my channels. I have set all the base fees to 0, following the movement
to support Pickhardt payments, and I have set my fee rates 20ppm, which I have
identified as being relatively low, so that I can check how much flows through
my node.
But at some point, I will want to get more serious about fee management.
Specially, taking into account the impact on balancing. Overall, balanced
channels are desirable since they give more paths to the network, and thus make
the node more capable of routing in different directions. At the entire node
level, it's also important to have a general balance between local and remote,
because that limits the total capacity of the node (i.e. if you have 10M sats
of outbound capacity, but no inbound capacity at all, you can't route anything.
The other way around holds true as well.).
To achieve this, I have been looking into `charge-lnd`. The tool is a small
python script that can read data from `lnd` and modify fees accordingly. There
are some instructions on how to set it up with umbrel, which is awesome. The
tool is configurable through a very simple config file that allows several
policies to exist, so a pretty intelligent behaviour can be achieved with
relatively simple effort.
The link to the tool is: [github](https://github.com/accumulator/charge-lnd)
I also found this example gist showcasing some example policies, which I think
will be very
useful: [the gist](https://gist.github.com/ziggie1984/48a67f3ee3cd0616e40620dc372ac3fe)
Eventually, I need to set this up. But I will still play around manually for a
while to get a feel on the behaviour of flows with different fees.