Perhaps their capital is only stucked in private channels and they haven't noticed yet. But that wouldn't be good for a Lightning Company either.
Discussion
There is also a probability that they want to discourage the activity unless it’s important and someone is willing to pay and not use them as a swapping service.
I have raised the issue directly with them and they brought it to the lightning devs in charge of the node. But then came back saying there is no issue.
So they are definitely aware but don’t seem to want to correct it or even admit the issue exists.
Are you still having issues? We just opened some channels, should resolve things
As far as I can tell from my position in the network, it’s still not possible to send directly via my Strike channel to lndus1.zaphq.io or lndus0.zaphq.io nodes which is where invoices generated on Strike app are directed to. Even very small amounts fail.
I can reach Strike (zaphq invoices) via other channels such as Bitfinex and Kraken, but generally the Strike node itself seems mostly unusable for nearly all routes I have tried over the past few days, and seems mostly depleted of outbound.
I do see some fresh channels to the zaphq nodes in the graph so perhaps it may just take some time for them to propagate to gossip for routing. Hopefully that will alleviate the issues I’ve been noticing lately 🤞thanks for jumping in nostr:npub1cn4t4cd78nm900qc2hhqte5aa8c9njm6qkfzw95tszufwcwtcnsq7g3vle
Hey Jack, not much has really changed since yesterday. The number of channels with 5000 ppm has remained roughly the same. They had brought about a temporary improvement, but now they seem to be depleting again.
wow, LN usage is exploding right now. will handle it, thanks for the ping