Replying to Avatar Not Sure

I agree but I also don't agree. I'm not setting up LNURL and pointing at my node. Also I'm not putting my node's pub key in my nostr profile.
Avatar
Seth For Privacy 2y ago

Well, that's the other core issue -- LN's receive privacy is broken AF right now due to this and people should actually be wary of publicly linking their node.

Wish that wasn't the case but until Bolt12 etc. it's problematic.

Reply to this note

Please Login to reply.

Discussion

91
page394 2y ago

Can you quickly bulletpoint how bolt12 remedies this?

Avatar
Seth For Privacy 2y ago

BOLT-12 + alias SCIDs would allow you to not reveal your pubkey in each invoice, allowing you to do Zaps without linking Nostr to a single node.

Still has to be reachable via network, but can use VPN/Tor for your node to remedy that issue.

Avatar
Not Sure 2y ago

Does Bolt12 even really solve the privacy issue? It solves the 'need to create an invoice, or need post a node ID with keysend enabled, or setup a lnurl contraption issue'

Avatar
Not Sure 2y ago

Granted, I haven't done a deep dive in Bolt12.

Avatar
Seth For Privacy 2y ago

It doesn't solve it, but it does help to reduce exposure as a static pubkey isn't part of the invoice anymore, and then can use alias SCIDs and route blinding etc.

Still have to be able to reach your node, but VPN/Tor help there.