both are fine
Muun has often giving me errors with LNurl QR's; I prefer BW bc of it
maybe it's fixed by now tho, idk
Discussion
*given😗
Ah ok yes. Muun can’t pay to LNURL-pay, which is what’s used for tip buttons on here. I thought you were just looking for a quick way to swap from on chain to lightning. Muun is good for that. Send on chain to Muun. Then send lightning from Muun to another wallet that has good LNURL support
Interestingly, Muun works for me to send zaps, was surprised, not sure how it does since no LNURL support?
Because zaps (when you zap from the little button on a post) pulls a bolt11 invoice so Muun never actually sees the LNURL that way
To say this more clearly, it’s a different flow with zaps. With zaps the client uses the LNURL to request the bolt11 invoice and then passes that on to the paying wallet. With a non-zap payment, the wallet must be able to pull a bolt11 using LNURL, which Muun can’t do.
why the extra step when you can do this all with just bluewallet app?
Because BlueWallet default Lightning service sucks ass. Lol. If you’re using Blue connected to your own lightning node then it’s fine.
Why do all that when you can:
Open strike, put usd on your strike account, generate a lightning invoice on the lightning wallet that supports zaps, in the upper right corner of the Home Screen on strike click qr code icon, paste lightning invoice. Strike sends usd over the lightning network to your zap supported wallet. No price slippage or taxable event.
KYC