Quote from: o_e_l_e_o on Today at 03:57:46 PM

Quote from: Kruw on Today at 02:55:48 PM

I'm pointing out how the exact same solution for being censored in Joinmarket coinjoins is the same solution to being censored with WabiSabi coinjoins: Run your own coordinator.

You fundamentally do not understand how JoinMarket works. As the taker, I coordinate the coinjoin by selecting a variety of makers. If a maker wants to censor me, then my software will automatically pick another maker and I won't even realize it happened. If Wasabi wants to censor me, there is nothing I can do unless I want to spend days to weeks setting up and running my own coordinator and trying to entice a few hundreds users across to it.

No, I understand it perfectly: The way to prevent being censored as a maker in Joinmarket is to coordinate the transaction yourself (become a taker). This is exactly the same way to prevent being censored as a maker in WabiSabi - You coordinate the transaction yourself.

Quote from: o_e_l_e_o on Today at 03:57:46 PM

Quote from: Kruw on Today at 02:55:48 PM

Why is remixing coins not desirable?

I never said remixing is not desirable. I said remixing the same coins over and over with themselves is not desirable.

This concept does not apply to WabiSabi coinjoins. The outputs merged into the next coinjoin can be owned by multiple participants or even entirely new participants who did not own an input from the original round at all.

Quote from: o_e_l_e_o on Today at 03:57:46 PM

Quote from: Kruw on Today at 02:55:48 PM

I don't know, it seems like this is another case of multiple clients using the same seed causing address collision: https://twitter.com/yahiheb_/status/1587161913531797504

So many people running two instances of Wasabi with the same seed! Still, makes for convenient excuse for literally every problem. Roll Eyes

It's an obvious explanation for a single problem, which is address reuse. You can't seem to understand this is a property of hierarchical deterministic address generation (https://bips.xyz/32) despite having already been shown multiple examples of address reuse in Samourai wallet:

Quote from: Kruw on April 14, 2023, 12:53:35 PM

Quote from: o_e_l_e_o on April 14, 2023, 11:49:07 AM

Because Wasabi wallet automatically picks addresses?

If a JoinMarket user picks a reused address to send a coinjoin output to, that's their fault.
If a Wasabi client automatically picks a reused address to send a coinjoin output to with zero input or even awareness from the user, that's Wasabi's fault.

And what exactly do you think happens when you use the same seed on multiple clients? Here's your answer:

https://medium.com/@thepiratewhocantbenamed/samourai-wallet-address-reuse-bug-1d64d311983d
https://twitter.com/SamouraiWallet/status/1283145015124996098
https://twitter.com/brian_trollz/status/1559018534675644418

Quote from: o_e_l_e_o on Today at 03:57:46 PM

Quote from: Kruw on Today at 02:55:48 PM

...Which can happen to you in Joinmarket as well. You can get censored by the coordinator and you can't even detect they are doing this.

No, you can't. Makers can choose not to join your coinjoin, and so you can pick different makers instantly. They absolutely cannot ban you from coinjoining altogether like Wasabi can do. (I know you are going to repeat your nonsense soundbite about "run your own coordinator" here, but as I explained above, that simply is not an option for 99.9% of users).

Makers can get censored by coordinators and you can't even detect they are censoring you. The coordinator, which is the taker, can ban you from their round.

Quote from: o_e_l_e_o on Today at 03:57:46 PM

Quote from: Kruw on Today at 02:55:48 PM

Once again, no, those are not WabiSabi coinjoins.

Excuse after excuse. It's multiple clients, it was Wasabi not WabiSabi, it was Version 1 not Version 2, it was "acceptable" address reuse, it was a "whale", on and on and on. Maybe once try accepting ownership and say "Yeah, that's a bug, here's how we are going to address it"?

[/quote]

Where's the bug? Please show me in the code so we can fix it.