Post
Topic
Board Development & Technical Discussion
Re: Mixing Bitcoin twice in series in case your mixer is a bad actor or mixes poorly
by
Kristinnspence
on 16/05/2019, 09:11:07 UTC
Use of any one mixer comes down to trust. Trust that the mixing is sound, that the mixer is not compromised, and that it's not a honeypot to begin with.

Using two chained mixers mitigates most of this risk. Odds of having two bad mixers is far lower than just one.

To this end, I've written a Python 3 library and CLI for Privcoin, Foxcoin, and Bitmix. They can be used separately, like
Code:
pip3 install privcoin; privcoin mix --currency bitcoin --output_address 1aaaa...
,
Code:
pip3 install foxcoin; foxcoin mix --currency bitcoin --output_address 1aaaa...
, etc.

The improvement is using two mixers, together.

Code:
pip3 install doublemixer
Code:
doublemixer mix --currency bitcoin --output_address 1aaaa...

You may wish to run it with torsocks to route the traffic over Tor.

This is completely client side, so no need to trust a third party. Just be sure to review the code of privcoin-python, bitmix-python, and doublemixer-python before use. Absolutely no warranties expressed or implied, no liability on the author's behalf, etc.

Source code for doublemixer on Github

In action:



I can also make a browser (still 100% client side) version of this, both clearnet and a .onion if there's interest.

That's pretty smart, but if you are using both mixers then don't you have to pay the fees on each one separately ? so fees will rack up?