If the sending user has a Lightning-only wallet, then they have no choice: they can only pay via Lightning.
For wallets that support both on-chain and Lightning, it would be helpful to the user to default to the option that offers the lowest fees, which in most cases is going to be Lightning.
In edge cases where the on-chain fees are actually lower than Lightning, then the wallet could opt to send on-chain or even present the user which a choice: "You can save X amount on fees, but this transaction will take longer to confirm. Is this OK?"
Does that mean you can have a static QR and get repeated LN payments?
No, just that you have a QR code that can receive Lightning or on chain Bitcoin
deleted by author
deleted by author
Watch as the big corporations come to destroy Bitcoin UX.
In which ways do you expect big corporations to destroy Bitcoin UX?
What can the Bitcoin community do today to prevent that?
By trying to appeal to their dumb users and their vices instead of educating them.
Are you referring to self-custody education, or something else?
Are there any specific design choices for Unified QRs that you don't like?
deleted by author
deleted by author
deleted by author
what makes you think this is a bad UI/UX decision, i think this helps extrapolate away some things kinda like how MUUN does.
Muun is a fake wallet that cannot continue to work in the long run.
deleted by author
deleted by author
deleted by author
🐦 70% of payments from @CashApp to @Bitrefill are still using on-chain BTC instead of lightning | @MattAhlborg
#23962
https://twitter.com/MattAhlborg/status/1520068091580928001
https://cdn.decrypt.co/resize/1536/wp-content/uploads/2022/04/receive-gID_6.jpg
deleted by author
deleted by author
Cash app the best KYC exchange hands down!
deleted by author
deleted by author