You are using ln.coinos.io 021294fff596e497ad2902cd5f19673e9020953d90625d68c22e91b51a45c032d3
to receive zaps ⚡
Discussion
I want to congratulate nostr:nprofile1qqszfn67p6jlle0qsj7lwx2l0ylxpse83e0x56qe5euxtwgwnyzdfqgpz3mhxue69uhhyetvv9ujumn0wd68ytnww5q3vamnwvaz7tmjv4kxz7fwdehhxarj9e3xzmnyswfy07 for finding an LN transaction and posting it
Let's see info he learned:
- sender? Himself -- assuming he sent from a self-custodial wallet, he even knows the address or channel of the sender, wow!
- recipient? He knows the recipient's communication pubkey, node, and node name -- though not learn the address or channel that received the money
- Amount? 69 sats
- Fee? less than 1 sat
That's a lot of info! More than I'd get from analyzing a monero transaction.
Reading this back, it sounds sarcastic; it's not, I am being genuine: this really is more info than I'd get from analyzing a monero transaction, and it motivates me to work on making LN better. Thanks Kevin!
If you were using blinded paths I would not be able to tell the final recipient, so LN can already be more private for receivers 🕶️
Is there a thread with more context to this?
When you are sending the sats, then you have all the details, we knew that, right?
It's the same when I'm sending from Phoenix: I see the hops the payment went through, I see the target pubkey, preimage, amounts, fees.
I see my immediate channel to Phoenix ASP (and obviously my wallet descriptors, founding transaction, etc) and online I can find public channels from ACINQ to other nodes (ACINQ has a lot of those). You can put the hop id (node id) into mempool space and it shows the node details and channels.
The question is if you can catch some other transaction that you are not participating in. For that you would need to capture the packets going over the network with wireshark or log the info as a routing node.
Using blinded paths or Bolt12 should help (from what smart people say).