Also conflicted. I have custodial and non-custodial Lightning, but only custodial gives me an address.

Can we setup some sort of directory on a remote server, to facilitate zapping over any NIP 05, or something?

Reply to this note

Please Login to reply.

Discussion

Or am I missing something important and just showing my ignorance? 😂🙈

There's things like nostdress so you can link your wallet (lnd or lnbits) to a zapable lnaddress. You need a webserver/domain tho, so more advanced stuff.

I really mean wos being down in us, Alby needs invite codes etc.

Yeah, I have a webserver and domain, tho. Lots of people do. I was wondering if we could run something generic, for any confirmed NIP-05 address, rather than for some particular provider.

Like a... zapserver?

I guess I'm asking if we can completely change the architecture.

Not sure if I get it right. Nostdress provides you with a lnaddress and a nip05, hosted on your domain. But it still needs to know where to forward the zaps to

That actually sounds like a solution. They could forward to any address, including something self-hosted.

The problem is the receiving wallet has to generate the invoice. Since this happens over an http endpoint, the wallet has to run a web server.

Ah, I see. So, the wallet has to be located on the same server as the invoice? There's no way to redirect?

There are ways but like anything else with trade offs. If you can communicate with the wallet someway (like NWC) outside of http, the web server could fetch an invoice on behalf of the wallet.

If the receiving wallet is offline/unreachable - things get more tricky. Zeus does something with holdinvoices to let self-custodial wallet users claim the funds when they come online.

There always needs to be some coordination between the eventual receiver and the web server though.