Subnostr

You are sending the KYC sats to "someone" address, if anyone (ISP/Gob/etc) can use some data and meta data to identify that you have the keys to move the sats for that address, yes, you are doxxing yourself. If you use the ip from your ISP provider... more easy, they can sniff all the packages. If you use Tor, as you said...they have to put more work to identify you unless you said "Hey, this is my node and my address". In the end, if the big brother wants... can't track you and in the last instance... it's a true/false face to face interrogation to check if that node is owned by you.

If you start from the KYC sats... I only can think about some "I lost my keys", "Some body rob my key and send to some place I don't know about", "I lost my key in the street, maybe someone use it to move the corn to other place".

Any KYC sats need to be acumulate and in one action "lost" in a boat accident, or "other" people get your priv key and move to another place.

In that situation, this "other" person could send those sats to some coinjoin software and "clean it".

My 2cents

boston wine 2y ago

This helps a bit, thank you. I’m not really thinking about the privacy of the coins. Just the node - if Node X only broadcasts transactions filled with KYC’d UTXOs, does that effectively associate that particular node with the KYC’d identity?

Reply to this note

Please Login to reply.

Discussion

nikotsla 2y ago

I need to look at the code or read the specification, so ... take my point of view as someone how don't know every details of the flow. If I have the power to analyze the network traffic of public nodes (not tor) I could match the broadcast with the origin and then try to look who is the owner of the node.

boston wine 2y ago

That makes perfect sense. Seems that running one’s own node Tor-only would eliminate this risk, most likely.