Replying to Avatar Kruw

Reusing addresses is bad for privacy, there's no denying that at all.

But at the end of the day, Bitcoin is non custodial: Your keys, your coins. If you choose to send to an already used address, the coordinator can't do anything to stop you in a meaningful way.
Avatar
Meister Eder 2y ago

Don’t blame the user! I am talking about symmetric address reuse (same address used on both sides of the transaction)

Reply to this note

Please Login to reply.

Discussion

Avatar
Kruw 2y ago

Would it be fair to blame the user if they imported the seed into a second client running simultaneously? This would cause address collisions since each client is not aware of transactions the other is signing.

Avatar
Meister Eder 2y ago

That’s what I meant with „genuinely interested“. I condemn the cooperation of wasabi with chain anal. But I have a feeling the the adress reuse thing is an extreme provoked edge case. Hinting a weak coinjoin protocol but not really relevant in a practical use scenario

Avatar
Kruw 2y ago

I'm genuinely interested in what extreme edge cases would cause a client to reuse an address as well. Here's an example of address reuse regarding Samourai's client - https://twitter.com/brian_trollz/status/1283525347007442944

https://twitter.com/brian_trollz/status/1445065052118261776

But since address reuse is not a part of either coinjoin protocol itself, it's not really relevant to the solving the problem of "What is the best way to make non private inputs into private outputs without revealing any addresses belong to each other".