Nostr Web Client

> Bob has a BIP-353 compatible wallet and the wallet prepends the ₿ prefix and Bob chose to copy payment info from his client.

Bobs wallet should copy the bitcoin: URI according to the spec, not the human readable address. Only when Alice and Bob communicate via voice should they use the human readable address. As long as she doesn't type the B symbol then Bobs LNURL fallback will work.

Sjors Provoost 1y ago

I think you should see indeed BIP-353 as a replacement for LNURL, at least for the this specific purpose of paying someone. It's backwards compatible if the sender types an email-like address, but not in all other scenarios.

It's not just about not needing https. The other difference is that once you've obtained payment info from BIP-353 you have everything you need. Once you have the bolt12 offer everything is lightning protocol native.

With LNURL there's another back and forth to request the actual invoice (IIUC). This is why you can't copy the bitcoin: URI and give it to a wallet that only supports LNURL and bolt12. But you *can* give it to a wallet that supports bolt12 and neither LNURL or BIP-353.

(2) I don't think there's any versioning. BIP21 style bitcoin: URIs are flexible enough to add new stuff later.

Reply to this note

Please Login to reply.

Discussion

Sjors Provoost 1y ago

* "that only supports LNURL and bolt12" should be "that only supports LNURL and NOT bolt12"

Big Barry Bitcoin 1y ago

Okay, so with BIP353 implicitly comes support for BIP21 which I have not read through yet 🙈.

This would make sending bitcoin://sjors._bitcoin-payment.provoost.nl sensible then. Since the OS will find the appropriate wallet for the protocol. 👍

Also the protocol is bitcoin:// (obviously) 👍

Now I follow completely.

Thank you.

Big Barry Bitcoin 1y ago

Nevermind, I have read BIP21 💩

Sjors Provoost 1y ago

Unfortunately one downside of bitcoin: URIs is that they open a single app. On iOs you can't change which one and it's always the wrong one.