pull down to refresh

Pending withdrawals,
This was discussed in a post yesterday.
Everyone commenting thinks it's because cash app can't do lightning very well,
I think it's cash app wanting human verification or AML/KYC, or something like that before they permit a withdrawal to LN to happen, because the pattern seems to be if I just did a deposit or I just did a loaded cash using that vanilla reload service whatever it is, it's those that gets stuck.
So I don't know if it's cash app really doesn't know how to do the stupidly simple job of just paying an LN invoice, or cannot manage their channels, or whatever, or if cash app instead is using lightning "pending" status as a method of buying time until they can have something else approve that payment.
Anyway it's harming the user experience of using bitcoin. God I wish I got paid in Bitcoin so I didn't have to deal with these Fiat crappy pieces of s*** systems
it's their nodes and not charging a fee at all.
sometimes my lightning tx's go through immediately or within 2-3 minutes, then other times to the same wallet(s) it pends for hours or days then ultimately fails or sometimes goes through.
it's inconsistent as fuck because they're not charging routing fees to route our tx's. This causes our tx's to only be able to go through channels and nodes that are feeless...so it's difficult to find a route sometimes.
reply
Works every time for me. no problem ever. Literally every single lightning withdrawal or deposit to cashapp has went through every time in like 10 seconds.
reply
You're lucky.
reply
Have you taken a second to think it may be on your side? Are you running your own node? Are you using a wallet like phoenix wallet over tor only?......
reply
Today's first-hand experience.
Just got three LN withdrawals delivered (i.e., LN Invoices paid by Cash App), boom, boom, boom, one two three -- all at once. Two were stuck for nearly twelve hours, then finally reported as paid PAID (received) by WoS. The third was from just a few hours ago, but then now shows PAID (received) by WoS. Interestingly, all three still show "Pending" on Cash App, even after they now show as PAID on WoS.
A attempt, from nearly twelve hours ago, to pay a CoinOS.io invoice, was "Pending" for only for a handful of hours and then showed "Send Failed". Each attempt was for an amount ranging from $10 to $50 worth of bitcoin.
So that was Cash App going zero for four for me today, as far as what I consider to be "acceptable performance". I did eventually receive the funds for three of those attempts.
Customer support was involved after six hours of Pending, and still no resolution for two of the payments for many hours more.
Again ... Jack, .... please FIX YO SHIT!!!
reply
I don't have experience with it but https://www.bitwage.com/
reply
Yeah, I appreciate that suggestion. So I'm switching one Fiat exchange for another, except now instead of me dealing with the exchange it's my employer dealing with the exchange. I like that even less
Though I did learn that I can do with ADP, which my employer uses, is send some fraction of my check like a fixed amount of dollars each pay period to the direct deposit account I get from Strike. I would much rather do that than continue to patronize cash app which has been absolutely horrible yet because they're the most convenient and normally quickest I've been getting by with them but now I simply cannot continue using cash app without LN withdrawals working properly.
reply
strike disabled the direct deposit service recently stating "Due to an ongoing effort to upgrade our infrastructure, we are migrating direct deposit partners and have temporarily paused this service."
reply
Update: That's back working now
reply
reply
So I'm switching one Fiat exchange for another, except now instead of me dealing with the exchange it's my employer dealing with the exchange.
the employer doesn't even have to know about bitwage, afaik about how it works:
Bitwage works for everyone, even if your employer is not using our service.
reply
Previous days' post:
Has Cash App's Lightning network always been broken? #213652
reply