I don’t let myself get obsessed with balanced channels. As long as there’s good routing and overall liquidity I’m not going to micromanage. Let the strong channels survive.

Reply to this note

Please Login to reply.

Discussion

I just try to keep liquidity on both sides of the channel so it can route if an opportunity comes my way. If it gets too tight to one side I’ll rebalance. I’ve dropped my fees and it’s helped a lot with getting routes. Seeing some back and forth and some channels seem to stay in pretty good shape. 🤙🏻

+1 — I dont obsess over having every single one of my channels balanced at all times. Rather I make sure my overall capacity is somewhat balanced.

Main key to me has been managing the max HTLC number to match my local liquidity. I do this about 3 times a week. This has allowed liquidity to flow both ways in every single one of my channels. I haven’t had to do any manual rebalance in about a year!

I don’t understand htlc T all. Sometimes I see stuff locked up on my nose for a period but don’t know why or how

Same here. I had 50k locked up the other day for a 24 hours or so and it was between two of my channel partners. I think it was a payment that maybe didn’t get routed or something. It finally cleared.

Max HTLC’s essentially indicates to the network the maximum amount of payment you can/are willing to forward.

Let’s say you have a 1 million sat channel but only 321,210 sats on your side. By default the max HTLC’s is set to the channel capacity so here 1,000,000. However because you only have 321,210 sats locally, a forward payment of 1,000,000 would result in a failed payment which decreases the ‘reputation’ of your node to forward payment.

Therefore you need to set up your Max HTLC’s to 321,000. That way the network knows that it can only forward 321,000 sats payment or less through your channel ⚡️

Thanks mate. I will try this.

Do you know if there is a tool that can do this automatically. Seems there is a tool for everything else??

Absolutely, there’s definitely a script to manage Max HTLC’s. I do it manually as my breakfast routine but I think nostr:npub1q8gth72n0mcl6rwls905rsvfvuu0dgaq7cq028rc9d7c3ygnp4xq84awvk has an automated one.

This sounds like a good thing to learn about. I’d be down to making it a part of my morning routine as well. Could you give me a little insight to what you do? Do you adjust it based on sats on your side of each channel daily? Where do you do this? Thanks

Looks like I can do it in nostr:npub1xnf02f60r9v0e5kty33a404dm79zr7z2eepyrk5gsq3m7pwvsz2sazlpr5 I would assume I’d want to adjust it daily based on my side sats. So if I have outgoing capacity of say 750k sats, maybe I set it at 500k? Is that hour you’d handle it or would you set it at your total available each day? Thanks

Yep I usually do it in Zeus and I set it to super close to the total available on my side each day. If I have 750,225 sats, I’d do 750,000. If I have 1,234,670 I do 1,234,000 etc.

Thanks for the information 🤙🏻

I’ve been working on a bash script for this. Not quite in a shareable state yet, but getting close! #womm

Nice!!!

Thanks adpo. I look forward to trying it. Zapped followed. 🤝💪⚡️🧡

I’ve got it in an early, shareable state on github. RTFM, don’t be reckless, and all that jazz. 💜⚡️

https://github.com/adamporter/maxHTLC-me