It's going to be easy to implement lightning addresses from self custody soon.

Reply to this note

Please Login to reply.

Discussion

Even if Btcpayserver supports NIP-57, one’d still need to muck with their router to do a reverse proxy and have the RaspPi exposed clearnet to the internet.

I can now see why the Lightning community is such up in arms about LNURL and Lightning Lab’s reluctance to invest in #BOT12.

LNC + LN Address?

Took a quick read of LNC, but seems like it connects your browser to your node. So at the least your browser needs to be always on and act as a web server or something then?

Most plebs would have already downloaded Wallet of Satoshi by now.

LNC is an easy portal to connect your node to things. Doesn't have to go through browser, that is just a single use case for it

How can the outside world even see your node without a reverse proxy at the router level at least?

LNC has some router holepunching capabilities

Perhaps, but as it is it doesn’t seem it have implemented NIP-57. So WoS is still the only realistic way. And that’s what Zap did, onboarded a whole bunch of people to a LN custodial solution.

Yep!

I cannot find any info from 30 seconds of Brave Search that indicates this setup will generate LNURL with NIP-57. And not certain whether my browser needs to be always on to service LNURL requests.

It'll work through a relay of sorts. You can give an LNC login phrase dedicated to "invoice only" permissions on your node to a website (LightningAddress.com in this theoretical example) and then i could claim VariableFate@LightningAddress.com

Perhaps. But I can’t get it working. This is a dev with enough server knowledge to put a website on a VPS. Definitely no Lightning or networking expert. But I’d say 99.99% of people would just download a WoS if they really want to Zap, and that’s the anti-pattern I’m talking about.