ACINQ
Unable to scan lightning: URI with Lightning Address
Hi!
I'm unable to scan a lightning: URI QR code with Phoenix wallet (iOS) when the URI points to a Lightning Address.
It works as expected when the lightning: URI QR code links to a Bolt11 or LNURL.
Example 1) lightning:[email protected]
Error: This appears to be a website (not a lightning invoice)
Example 2) lightning:[email protected]
Error: This does not appear to be a Lightning invoice
Example 3) lightning:LNURL1DP68GURN8GHJ7UM9DEJZUMRPD9EK2EFWDAEXWTMVDE6HYMRS9A49QE2SGV6QHV9RY5
Success!
I second this, we had a LN address QR codes durinng a conference event with over 3000 transactions, Phoenix wallet was one of the few from which people couldn't tip to LN address printed qr. Would be good to get this fixed.
These two URIs are rejected because they mix a lightning: prefix with a LNURL-based address. This seems the correct behaviour to me, the expected format is <username>@<domainname>. The whole point of human-readable addresses is to make them not technical, short and memorable, so having a URI scheme prefix there does not make sense. Besides, using the lightning scheme is not recommended (see LUD17).
I second this, we had a LN address QR codes durinng a conference event with over 3000 transactions, Phoenix wallet was one of the few from which people couldn't tip to LN address printed qr. Would be good to get this fixed.
This could be an unrelated issue, could you share the address that was used?
The reason why we prefer to prefix lightning: to Lightning addresses is that otherwise, when people scan a Lightning address with their phone's integrated camera, they get directed to their email client.
Using the lightning: prefix allows the QR code to be scanned with the integrated camera app, they get redirected to their Lightning wallet and they get a visual confirmation of who they are sending money to.
The reason why we prefer to prefix
lightning:to Lightning addresses is that otherwise, when people scan a Lightning address with their phone's integrated camera, they get directed to their email client.
That's a good point, I see why the prefix would help. Will fix, thanks for reporting the issue.
Note that you may want to use the lnurlp: prefix instead, since the lightning: prefix could open a Lightning application that does not handle LNURL payments and would thus reject the address. It's an issue on iOS where the user cannot choose which app opens for a given prefix, so he would be stuck and unable to pay this address.