Which implementation?

Reply to this note

Please Login to reply.

Discussion

Not sure

Thinking it must be wasabi because whirlpool has all equal UTXO inputs and outputs

Yup, that's a Wasabi 2.0 coinjoin, they get quite big...

Wasabi is laptop desktop only right?

Yes.

But if you have a BTCPayServer, turn on the wabisabi coinjoin plugin, and you can batch payments inside a coinjoin from your phone browser.

Mobile App in the future or no?

It's very difficult to build an anonymous mobil wallet. It will take a couple more years before we have something great, I'd guess.

In oh, Wassabi coin join if you use multiple UTEXO’s as inputs would you be able to see on Shein that there was a common owner before the coin joint?

Voice to text. Sorry.

No, not even the coordinator learns if multiple inputs belong to the same user.

Each input is registered with a fresh Tor identity, and received a anonymous credential for the exact amount of the input value.

Multiple Tor identities, or anonymous credentials, cannot be linked to each other, so the coordinator knows only what everyone else sees on the blockchain.

How does the fee structure work you pay per input? And is it like a flat fee or a percentage?

Yes, per input a 0.3% fee, but only for coins larger than 1 mil sats and only when they don't come from a previous coinjoin.

Thanks for the info I’ll have to check it out

Let me know when you have any questions or improvements.

Thanks Max

Another fun challenge for those coinjojns:

Which input or output comes from which client implementation?

Wasabi, Trezor, BTCPay, some other private custom client?