A few days ago, I wanted to pay with lightning in a coffee shop but scanning the QR code with Phoenix resulted in "unknown data" iirc. The text below the QR code read lnurlp://<pubkey>@<ip> or something like that. The employee then used a different device where I was able to scan the QR code and pay with no issues. That one showed lnurl... as I am used to (again, iirc).
Anyone knows what's up with this lnurlp:// and why Phoenix doesn't support it?
If Phoenix is open source be sure to create an issue in their tracker if one doesn't exist. If it's not, then contact customer support. One way or another these little things have to be found and fixed.
reply
Good point. It is OSS: https://github.com/ACINQ/phoenix
I'll try to reproduce the issue and will then create a ticket. Maybe I'll even try to fix it myself :)
reply
Seems that was a wrong generated QR.
reply
They were using BTCPay Server so it generating "wrong" QRs is weird
reply
That doesn't mean it was generated by that btcpay server lnurlp://<pubkey>@<ip> is wrong
here are the specs for lnurlp https://github.com/lnurl/luds/blob/luds/06.md
reply