silenzara / Silen Zara is on Nostr

lightning node operator

Last Notes

2024-02-02 09:04:34

- reply

Thank you for always being a good peer to me. Lots of sats went through our channels. Good luck!

2024-01-18 16:34:39

I often see my peers increasing their fee to me by a very small amount (5 ppm or less). To me this makes very little sense because you risk losing traffic due to FEE_INSUFFICIENT errors (until the update is propagated through the network) for only a very small gain in profit.
That's why I use a lower limit on my fee increases. A reasonable amount I personally use is to take the square root of the current fee and use that as a minimum. For (very) low fee rate channels you can override this minimum to something like 10 and for higher fee rate channels maybe something round 25.
It becomes even more important if you want to serve transaction from lightning users who are not online all the time and can have a very outdated view of the network.
So if you want to maximize your chances of getting routes through your node (which you should) then you've got to be considerate about how you do fee updates.

2023-10-17 07:52:26

- reply

A solution for this "bloated" node problem is pairwise fees.

2023-10-17 07:44:13

Graph centrality is an overrated metric for pure routing nodes if they want to optimize their capital efficiency.
With more peers it becomes increasingly difficult to make them all flow. If you want to optimize APY then it's often better to have smaller, more specialized nodes that have all channels working together "in the same flow".

2023-05-22 17:04:47

- reply

Ockham's broom.

2023-03-31 06:29:40

- reply

I've used it for a few weeks now since the early rc's. I have a good experience with it so far, getting succes with some really long routes when rebalancing.
Haven't tweaked it's parameters yet but will try it soon.

2023-03-03 09:59:30

There's a lot of information to be learned by observing the payments flowing through a routing node. By having eyes on every payment, over time you will build up intuition about which routes are important to your node.
Eventually you will spot patterns and then the fun starts in figuring out how to increase (or decrease!) the probability of those patterns occuring. It can be tricky to spot those patterns because cause and effect are not obvious and seem decoupled without the right intuitions.
This is the core concept of running a successful routing node.