I have contacted nostr:nprofile1qqsvn0dkjt80raqrxd470c98n7zrdehmcvj6p5hgw3kyku6zyd8z0fqpz3mhxue69uhhyetvv9ujuerpd46hxtnfduq3qamnwvaz7tmwdaehgu3wwa5kuegufe9k5 customer support about this same issue a number of times over the past few days and they insist there is no problem.

It is basically IMPOSSIBLE to deposit to Strike wallet right now unless you are willing to pay 0.5% to do so. nostr:nprofile1qqsvf646uxlreajhhsv9tms9u6w7nuzeedaqty38z69cpwyhv89ufcqpz3mhxue69uhhyetvv9ujuerpd46hxtnfduq3samnwvaz7tmjv4kxz7fwwdhx7un59eek7cmfv9kqfa3z5x you really should fix the situation, lots of customers are complaining.

Reply to this note

Please Login to reply.

Discussion

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.

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.

Then their node should have significantly more outbound than inbound liquidity to make them harder to reach. Currently, the opposite is the case.

Agree, it’s very strange they don’t seem to understand even the basics of what’s going on behind the scenes.

Interesting.

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

nostr:nprofile1qqsvlxz80x9jvpsmaut6yf76jv3ret7e2wgt6sjwzsk6qphykyq3fmspzemhxue69uhky6t5vdhkjmn9wgh8xmmrd9skcqg4waehxw309ajkgetw9ehx7um5wghxcctwvsaluctf nostr:nprofile1qqsvf646uxlreajhhsv9tms9u6w7nuzeedaqty38z69cpwyhv89ufcqpp4mhxue69uhkummn9ekx7mqpr4mhxue69uhkummnw3ez6ur4vgh8wetvd3hhyer9wghxuet5tm8sjr 👀

They are actually perfectly reachable at rates that are even lower than what they have been for the past few weeks. It's just that you can't reach them via the Strike node that indeed seems to suffer from outbound liquidity issues.

Strike (through the Zap nodes) are actually one of the few places that is still holding up during all the activity that has been going on for a while now.

Yes, exactly. Sending directly via the Strike node was the issue was that was being looked into. Lots of noderunners and average customers have direct channels to Strike for that very reason.

They have opened a few fresh channels between Strike and the zaphq nodes, hopefully that will alleviate some of the bottleneck ⚡️