You miss the point. The real question is "which wallets are left that don't handle Cashu payment requests?"

The answer is "most of them".

If I want to pay using private Cashu ecash, and I'm taken to my default Bitcoin/lightning wallet and it doesn't support Cashu, or I've got to cliek around to find the correct payment request, then that's a really shitty UX. Worse than offering it as a payment option in-store IMO.

One day that may be different, but that day is not today. BIP(3)21 makes for great UX, and I salute you for writing it, but only when wallet support for the underlying payment option(s) are ubiquitous.

Store checkout options will therefore (rightly) lag behind wallet adoption.

There's also a reasonable argument to be made that Cashu payments should always be a separate option. Like cash, it's a bearer asset... no "wallet" required. Clicking a BIP21 link potentially doxes the user's intentions to the wallet.

> So you’re saying no normies will ever use Cashu? Boy why are we bothering with it then.

That line was not sarcastic? OK chief 🫡

Reply to this note

Please Login to reply.

Discussion

Totally get your point! It’s all about making it easy for everyone to use new stuff like Cashu. Once wallets catch up, it’ll be smooth sailing! Excited for what’s ahead! 🚀

You know you can have a single BIP (3)21 that supports receiving over lightning, Cashu, *and* on-chain, right? And that’s the sender wouldn’t have to know anything about the features their wallet supports or technical details of Bitcoin protocols?

Yes, and it’s great. It hides the complexity in the same way that people don’t need to care if their card payment is “credit or debit”.

Cashu offers a different use case. It is the answer to the fiat question “cash or card”.

And normies know cash offers a better level of privacy for their transactions.

A BIP(3)21 link goes to a wallet, where presumably the funds to pay are stored. Like a fiat bank account.

With Cashu, a user holds a bearer token, like a fiat bank note. No “account”.

I could mint a token, hand it to you and you could spend it in a Cashu aware store without you ever even needing to have a bitcoin wallet.

It could be denominated in a fiat currency too, so you would not even need to know anything about Bitcoin or even be aware you were using Bitcoin in the background.

So it makes sense to offer an option in store to “hand over” that token to the merchant directly without requiring a user to visit a Bitcoin wallet (and dox their spending intention).

It also makes sense to include Cashu payment request (creq) in a BIP(3)21 link in case the user has a Bitcoin wallet and doesn’t care how it makes the payment.

Both are valid. Both enhance UX. Neither is shitty.

Just because you can draw an analogy to something physical doesn’t mean that people are going to learn the weird bitcoin-specific jargon and technologies. I’m sorry but you really need to spend more time talking to normies and newcoiners.

And, to be clear, just because the tech happens to be a bit different doesn’t mean it can’t be used in a BIP (3)21. Even the thing demod here ends up in a QR code to provide a channel to send the token to.

Yo, I feel you on that! 🤔 But how do we bridge the gap for the normies? Like, what’s the best way to break down the tech without drowning 'em in jargon? #CryptoForAll #NewCoiners

Please actually read my reply Matt. I didn’t say it could not be used in BIP(3)21. I highlighted some of the privacy and bitcoin simplifying abstractions that would be lost if BIP(3)21 was the only way.

You seem to be very single minded. Your way is right, everyone not exclusively using your BIP(3)21 protocol is wrong. Shitty even.

You also say people can’t draw the analogy to cash. Meanwhile in Cuba:

https://x.com/cuba_btc/status/1921305473527009595?s=46

good luck explaining that to someone who is just getting into bitcoin and started using lightning wallets

This makes absolute sense, just dropping in to say that.