My soft brain could really use some help understanding why my wallet can't read an LNURL. I know that QR codes have to present static information, so when I get an LNURL from one of these, I believe there's been a trick used somewhere to protect the recipient's privacy. I'm just a little muddy on that. What type of guidance would you give if I'm in front of you scanning a QR code and my wallet says "Please scan a valid lightning address." Are we using QR codes for everything and if so, I guess I need a different wallet??
334 sats \ 0 replies \ @0000 21 Jun 2023
It is possible the wallet you are using does not support LNURL Auth.
A list of wallets that do:
Alby
Balance of Satoshis
Blixt
Breez
Blue Wallet
Coinos
LNBits
LNtxtbot
Phoenix
Simple Bitcoin Wallet
Sparrow Wallet
ThunderHub
Zap Desktop
Zeus
The generated URL contains nothing private. It is basically just the domain of the service, for example stackernews with a few url parameters that define if its for logging in or signing up and then a random 32 byte string. The QR code just makes it easy to transmit between devices but services will also provide an encoded LNURL string.
The wallet will sign that random string and submit it back to the service to authenticate.
So for a wallet to support LNURL it must
- decode LNURL strings
- sign the random 32 bytes of data
- submit to the service to authenticate with that signature.
reply
144 sats \ 0 replies \ @DarthCoin 21 Jun 2023
Put your LNURL here and see what is decoded.
https://lnurl.fiatjaf.com/codec/
Maybe your LNURL server is not serving the correct response or is not visible over https.
LNURL = a web server that is requesting a LN invoice from a node and delivered to the wallet is requesting it.
LN address = is just a human readable LNURL.
Here is a guide about using LN address in many different ways:
https://darthcoin.substack.com/p/getting-started-lightning-address
And here is the list of all LN wallets that support various LNURL types
https://github.com/lnurl/luds#lnurl-documents
reply