pull down to refresh
Then I'm not sure I understand what you mean by "payment spec".
Imagine you're at a farmers market and want to buy a thing
"Bitcoin/Lightning Accepted Here"
You go to scan the QR with your lightning wallet at the PoS, low and behold its some trash fiat spec your wallet can't pay because it's not really Lightning
Or it's extra slow because of the swap/settlement between mints
Or it fails because of all the added complexity overlaid in settlement
This adds friction, confusion, and general bifurcation of the network effect of Lightning
Have you ever tried ecash? Cashu (and I think Fedimint as well) are very well integrated with lightning. Paying invoices works like the average lightning user would expect.
They don't "integrate", stop using words you don't know the meaning of
There is inherently more latency and failure probability as a result of the additional mint settlement overhead, this is engineering 101 and unavoidable when complexity is added.
Again, have you ever even used an ecash wallet? It's not practically slower than normal lightning. And by "integrate" I mean integrate in a UX sense. Please don't assume I don't know what I'm saying. I do use precise language.
Yes, had a good chuckle with some other Lightning wallet devs when we got rugged right away
I've also helped users of them decipher their bad error handling
I don't criticize the implementations directly because building shit is hard, its more fair just to say their ideas are stupid
How'd you get rugged? What ecash protocol did you use? What mint?
I used an ecash wallet as a primary wallet and had no problem.
I don't criticize the implementations directly because building shit is hard
We put sats in and couldn't get them out due to an error that made no sense
We reported it
I used an ecash wallet as a primary wallet and had no problem
Cool story, maybe our bug report helped... but it means nothing at scale