I call identifying the recipient "tracing" it
But you keep doing you, friend
looks like Digit's in denial
when someone identifies the recipient's pubkey in a bitcoin transaction, monero bros always seem happy to call that tracing
when someone does it to monero, they suddenly want to change the definition
"It's not tracing when you do it to US!"
(1) Run your own lightning node, I recommend electrum
(2) When you make an invoice, pass it through lnproxy: https://lnproxy.org
(3) Encourage more folks to run an lnproxy server so that your anonymity set grows
(4) On that note, this doesn't help *your* privacy but you can help other people get better privacy by running an lnproxy server. Learn more here: https://github.com/lnproxy/lnproxy
I don't know what you mean. It is software, therefore it is automatic. If you mean "how do I write/run the software," that's why I linked you to an implementation.
Where I can learn more about trampoling routing and decoy pubkey?
nostr:nprofile1qqs0nt9skq6vfsgh06v979rrnuchau87mmnk2lqxpv2xaeusqfp30mqpz3mhxue69uhkzmr8duh82arcduhx7mn99uq3wamnwvaz7tmzd96xxmmfdejhytnnda3kjctv9uqsuamnwvaz7tmwdaejumr0dshsvkk925 do you have this in any of your nice blogs?
There are several resources:
lnproxy.org/about.html <-- this is probably the easiest to understand and use
https://github.com/lightning/bolts/blob/master/proposals/route-blinding.md <-- this provides a more technical description
Several wallets support this privacy technique. Zeus wallet has a toggle in Settings to turn on "route blinding" (that's what they call it, it goes by several names). Phoenix Wallet also supports it if you use bolt12, because route blinding is used by default in bolt12 offers. But bolt11 can do it too, it's just not done by default in any bolt11 wallet that I know of.
I have an implementation of something similar to zap splits here: https://supertestnet.github.io/nwc_prisms/
You can peep the code easily as it is all in that html file. I don't know how amethyst does it, but how I do it is, I collect all the lightning addresses of the recipients, make one invoice which the zapper pays, and then my software "manually" (technicality, it's automatic now, because it's software) pays a percentage to each of the lightning addresses in the list. It's not atomic, and I don't think Amethyst's implementation is atomic either. But it seems to work well enough.
Lnproxy is very cool
Peep this nostr thread.
Big difference between lightning and monero: this random XMR user admits he doesn't have the resources to trace an LN payment. I, a random LN user, can provably trace an XMR payment. Anyone can, because monero is designed to be trivially sender-traceable.
Monero is surveillance money. I recommend using lightning instead.
My favorite part of the thread is where Kortik tries to identify the destination of my lightning invoice. He gets it wrong, of course, but he learns about trampoline routing along the way!
Big difference between lightning and monero: you, a random nostr user, admit you don't have the resources to trace a lightning payment. I, a random nostr user, can provably trace a monero payment. Anyone can, because monero is designed to be trivially sender-traceable.
Monero is surveillance money. I recommend using lightning.
Big difference between lightning and monero: you, a random nostr user, admit you don't have the resources to trace a lightning payment. I, a random nostr user, can provably trace a monero payment. Anyone can, because monero is designed to be trivially sender-traceable.
Monero is surveillance money. I recommend using lightning.
I used trampoline routing with a decoy pubkey. Meaning you got the wrong recipient. The actual recipient was Tating Turnup on nostr; Epic Astronaut merely runs a routing node. (See lnproxy.org for more on how this works.) Meaning if you were a chain analyst, you are now stuck watching the wrong pubkey! You've been led on a wild goose chase. Even if Epic Astronaut closes his channel, you'll be following the wrong person's money. Decpy pubkeys is a trick lightning can do but monero can't.
"Add Your Email" -- "We need to verify you're a real person"
Ick, no you don't 
Any bitcoiners in Des Moines, Iowa? I'm here for a month and would love to hang out!
I like FCMP and it sounds like it does fix most of my monero criticisms
But it fixes them by achieving what we already have in lightning (a blob of indecipherable sender data that anyone could have produced), and it achieves it in a way that unnecessarily bloats the chain with big blobs that everyone has to store forever
Just use lightning, that's my recommendation
Re: the sender tracing his payment to the recipient in a post FCMP world, yes, even in that world (if it ever arrives) the sender will be able to identify the recipient’s pubkey, which is tracing -- it's the first step. I think it's a lot less useful in a post FCMP world because every future tx will reference that pubkey as a possible spender, along with every other pubkey, and I suspect it will be infeasible to eliminate enough decoys in that world. Exiting stuff!
If every routing node colludes the best they can do is point to a node and say "that one was the next hop back and did not collude with us"
It might be your node, it might not be -- either way, they have no proof of wrongdoing
It seems to me that when the subject is "what pubkey key receives the money" it is entirely relevant to discuss whether the pubkey in a bolt11 invoice receives any money
Subaddresses are cool but they two unfortunate characteristics: (1) the sender derives a real pubkey from the subaddress and sends money to it (2) if the recipient spends that money, their pubkey shows up again as a member of a ring signature
Chain analysts use that fact to trace monero payments. They have ways to eliminate decoys from the ring signature and, in many cases, identify the real spender, and this privacy flaw has led to several arrests. Lightning fixes it.