I don't understand why lnurl-over-tor is not embraced by wallets and LN node software.

LND/CLN/ACINQ/LDK could create a tor hidden service and passively listen to invoice requests. They would thus have lnurl built-in support without the need for separate software (satdress, btcpayserver, ligess, etc), a domain name and ports 443/80 open.

Wallets could just support fetching invoices from onion addresses by leveraging their existent Tor support.

It would immensely help lnurl usage for users running their own node.

I know that bolt12 should obsolete lnurl, but until it actually ships, lnurl-over-tor should be an easy fix.

Reply to this note

Please Login to reply.

Discussion

#[2]โ€‹ is this something youโ€™re thinking about?

I @ them sometimes ago about it, I recall Evan said "sure why not", but a few releases later and it still does not work ๐Ÿ˜ช

Well, heโ€™s been kinda busy these days.

Initial support is in v0.7.5. You either have to be connecting to your node over Tor to use it or use Orbot in VPN mode.

My issue is with Orbot VPN mode activated for Zeus, I can no longer access my node.

There's a working LNURL-over-nostr and LNURL-over-email , see Oak Node on Umbrel.

It has a bot interface (over Nostr DMs or over PGP-encrypted email) and can do most basic LNURL-style operations: https://oak-node.net/file?name=doc/ons/ons-1.md&ci=trunk