Nostr Zap surveillance tech: https://zaplife.lol
This is what happens when "convenience" not privacy is the default setting. Sure its a "choice we are all making" but damn.....
I run multiple nodes and hesitated to connect my nostr account to any of them because I didn't want this account associated to nodes I use IRL for real #Bitcoin. I guess I need to spin up another nostr only node now.
Even though I agree on the overall point of LN receive privacy issues, important to note that privacy is "selectively revealing oneself to the world", and Zaps are only useful if they are revealed to the world in some fashion.
But definitely a huge issue that you have to link an LN node with static pubkey to do Zaps in a non-custodial fashion ATM.
I don’t see any point sending zaps from my node, I’ve been using Phoenix so still non-custodial. Also using Alby to receive LN payments. These aren’t large amounts of sats so I think the using some custodial servers to receive is ok as it adds a lot of convenience
This is what I love about Nostr nothing but reasonable informed takes:
Nostr Zap surveillance tech: https://zaplife.lol
Zaps are only useful if they are revealed to the world in some fashion. Zaps are a week old; better/easier support will come.
You can spin up a CLN with the zap plugin and isolate its publey just for zaps. Check @jb55’s github; there’s a repo for the plugin (the standalone script).
Simple attempts at obfuscating pubkey while still using the same underlying static node doesn't really do any hiding if you look at the invoice. We need better tools and wallets around lightning privacy and that's what I really hope we can solve at Mutiny. #[1]
Same, i will run different node for nostr only later.
Currently, using stacker.news to stack zaps and slowly send it several hops to my node
SN > OBW Wallet (Have different pubkey node each invoice) > Another Non Custodial Wallet > My Node
