If you have a self-hosted Lightning address, I'm much more generous with Zaps.

Proof of work.

Reply to this note

Please Login to reply.

Discussion

🤝

self-hosted on private domains are for private use, not for public use (like nostr zaps). Why would I give too much information in a public place for some zaps received?

Custodial LN address could be a good decoy too. Receive and withdraw, nothing burger and keep your other nodes and destination wallets, private.

What the hell are you talking about 🤣

Domains are inherently public, that's the entire point.

But only specific people will know about my domains used for specific payments.

Self-hosting LN address means you link a payment to that domain, that maybe you want to use it only in private, for specific payments.

Self-hosting LN address also means linked to a specific node, that maybe I do not want to make it public or linked to my identity.

I think you have limited perspective about what really is privacy. Privacy is not all about how to hide or avoid custodial, but is more not linking private info to public payments.

Custodial non-KYC ARE A PERFECT DECOY TO AVOID THAT LINK.

You've gone off on some autistic note storm about something entirely different to what I was saying 🤣

If you're setup works, good for you man. Not here to tell anyone how to use LN or Nostr.

* your

Please show me where the sats you zap me to my LN address on nostr are going. Did you know the final destination?

The answer is simple: NO.

But if you use a self-hosted LN address linked to your own self-hosted node, It will be quite easy for anybody to find out...

You see what I mean?

Again... custodial (non-KYC) are a perfect DECOY for the public zaps.

Let's cut the crap with this crazy "self-custodial" everything when is not really necessary this paranoia.

I have been trying for weeks. Will get it figured out one day.

BTCPay makes it fairly straightforward. Happy to help if you wanna DM

I got a cloudflare tunnel set up to BTCPay (pay.structur3.io) but the lighting address is still a local address. So far no answer on how to fix that in my search and inquiries.

https://nostrcheck.me/media/134743ca8ad0203b3657c20a6869e64f160ce48ae6388dc1f5ca67f346019ee7/e8acdea655697cfbdb068b0aa15fade79e979364846cd0875d336e967798ed73.webp

I just sent 21 sats to satstackingpleb@pay.structur3.io from my node.

It's working fine.

Shut the fuck up!!!!

duude, zapping it myself now. It just wasn't intuitive since the UI displays local address. bruh 🙏 🧡

It shows local because you're logging in locally. Log in from the domain and you'll see the domain LN address

Most people could just use their own domain and proxy lnurlp requests to a custodial lnurl provider, so even someone using their domain might be bullshiting.

I did that temporarily and proxied my domain's lnurl yo zeuspay while my lnd was broken.

Fair comment, but I think the majority of people with the knowhow to do so likely have the skill to run everything to their own node.