pull down to refresh

A question for those of you who are building on LN or running a service on LN:
How often does your application or service stop functioning because of LN liquidity, and how much time do you spend on resolving/preventing these types of issues (rebalances)?
reply
I am not advocating for rebalancing— I'm asking how much hassle liquidity management is for builders who require constant liquidity for their applications to function.
reply
All depends of:
  • what you really want to achieve
  • what you want to do with that LN node
  • how high is your greed
  • how high is your desire to FUCK THE BANKS
Read my guides and you will discover things that almost nobody wants to talk about.
reply
Again, this is in no relation to the question I'm asking.
reply
If you read you will know. Don't look for quick answers.
reply
I will implore you to take your own advice here.
I am not asking how I solve the issue for myself. I'm asking how many people experience this issue and how long they spend trying to mitigate it.
reply
Again, you don't even read my first link and you jumped into conclusions. https://darthcoin.substack.com/p/lightning-routing-fees-experiment
As a founder of a LN software you should already know how LN liquidity works. I was just giving you some clues after several testing with many nodes.
Liquidity is very important for a LN node, because have to flow. If you want to make it flow, think about WHY. And some clues are in my articles.
reply
Dude, he is not asking about how to run a routing node. He's asking about managing services on top of a LN node.
Maybe you should reach out to some known node operators who are running services. lightning.store is a good example.
reply
Definitely speaking to businesses running LN services. I will reach out to the lightning.store team though! They're a great example that would face these issues.
reply
almost never. Just opened a few good channels and then I send out the amount I make to my own node with a script every X hours/days.
My main problem is I have no idea to understand how often payments are failing to my node. It would be great if I could know when people try to pay and fail. But need to mostly depend on complaints.
reply
Ah interesting! A script running on a cron?
I guess having something to observe the channel state and issue payments would give a little more flexibility for failed payments?
reply
that's the only metric I track and try to improve. Currently about %10 of invoices are actually settled as payments. But this includes:
  • people that created an order but dont have a Lightning wallet
  • people that decided the amount was too high, didnt want to pay
  • order didnt go through for any other reason.
reply