"Unsupported LNURL request: error"

[HamishMacEwan]

The response to an LNbits "Quick Voucher" from http://ub3fenqxnexutnauxkekj2lvagmlpzga7el77jglyevfowuorj26skid.onion:5000/withdraw/CRkLCQKERa6VfjhP77AzTB:

LNURL1DP68GUP69UHNGDT4DP3KKUEJX44HJVN4W4ENVEMGV3NKZVMTD5EKUDNWW36HVVEHX4NKWMF5WPMRWUR8XACRGDMVWDC8V6T0D9UKGTN0DE5K7M36X5CRQVP0WA5HG6RYWFSHWTMPWP5J7A339AKXUATJDSH4S5TCTPT8W7RRF4T427TCXFM52VMP24XYZ330GGU8YUJPG3VXSCENVYEK6DTD2EN8ZKFH09TQMA00FV

Decodes to: http://45uhcks25ky2uus6ghdga3km3n6ntuv375ggm4pv7pg7p47lspvioiyd.onion:5000/withdraw/api/v1/lnurl/XQxXVwxcMWUyx2wE3aULAF/B8rrADXhc3a3m5mVfqY7yV

And Blixt with Tor enabled responds:

The LNURLw works as expected with Simple Bitcoin Wallet

[hsjoberg]

Thank your opening this issue @HamishMacEwan.

I think this could relate to one of these two things (or both):

1. Are you using the embedded Tor client? If so LNURL over Tor is not supported
2. If quick withdraw refers to LUD-08, that is also not supported right now

[HamishMacEwan]

Thank you for your prompt reply @hsjoberg . With all the shenanigans going on I'd expected to be patient. Very pleased to read your services will return soon.

1. "Blixt with Tor enabled" and for a time I worried that Orbot and the built-in nodes might not play well together. Tor, with http:// prefix is valid, only https:// is forbidden based on misunderstandings about the present and eventual supply of CA certificates to support Tor v3 addresses.

LNURL is acceptable in two forms: either an https:// clearnet link (no self-signed certificates allowed) or an http:// v2/v3 onion link.

https://github.com/fiatjaf/lnurl-rfc/blob/luds/01.md#https-or-onion

2. The information at the link provided seems to indicate this is a https://github.com/fiatjaf/lnurl-rfc/blob/luds/03.md compliant "withdrawRequest base spec." Which Blixt does support.

{
  "callback": "http://45uhcks25ky2uus6ghdga3km3n6ntuv375ggm4pv7pg7p47lspvioiyd.onion:5000/withdraw/api/v1/lnurl/cb/XQxXVwxcMWUyx2wE3aULAF", 
  "defaultDescription": "vouchers", 
  "k1": "bUwVCyrt2VHSB63wPAjFs2", 
  "maxWithdrawable": 100000, 
  "minWithdrawable": 100000, 
  "tag": "withdrawRequest"
}

I'm puzzled at your response, because all I know about these details has been tutored to me by you on Telegram in LNURL Mafia. I tested my compliance by using Simple Bitcoin Wallet, which I mentioned honoured the request before bothering you with this report.

Thank you again for the response.

"The real problem is that programmers have spent far too much time worrying about efficiency in the wrong places and at the wrong times; premature optimization is the root of all evil (or at least most of it) in programming."