Lightning is awesome, when it works.
I have an LNbits instance, it's mostly working when I test at home, but when I need it on the field, it's hit or miss. One day NWC stop working, zap are not passing though, next time I have the restart the app, another time it's the PoS that give strange errors for no reasons.
Then you have the transactions failing even when liquidity is here at all steps until destination.
And I'm not even talking about wallets, when it works smoothly it's custodial (or worst, Spark, nothing to do with Lightning), when it's not custodial you have all the limitations of Lightning but with no explanation, like Phoenix, we try to onboard no coiners, you test sending 500sats... Nothing happen. Then the user see a message that amount is too low and wondering what happened. End up sending 10 bucks at once first (to open a channel) but it cost 1000 sats (1% with 1000 sats minimum) for the service, much more than on chain cost. Not a great first user experience.
In the end the bar where we do the meetup is fine accepting onchain payement even without waiting for transaction, it's not even as risky as a charge back on credit card, and even if someone try to trick you once with double spend by resending to another address with higher fee, he will just get kicked of the bar forever, not really worth it and you will not dedicate your life buy eating free everyday at s new bitcoin accepting restaurant, restaurant where you anyway pay when you have already consumed. I know long term if we all use bitcoins it will not be possible but still, it proof how far with are with Lightning UX overall.
Login to reply
Replies (1)
Like lightning, animal fat is unreliable unless you feed it consistently, try a carnivore diet.