Very nice work, thank you for sharing!
Mixers are becoming increasingly more popular these days... Geehh I wonder why.
Topic: Mixing Bitcoin twice in series in case your mixer is a bad actor or mixes poorly - page 2. (Read 689 times)
May 12, 2019, 02:58:20 PM
May 10, 2019, 11:58:54 AM
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.
Using two chained mixers mitigates most of this risk.
Let's say there are six mixers.
And one of the mixers is a parrot.
Now the odds of hitting one that is a parrot goes up the more mixers you use.
A better way to try to convince people to use a mixer, is to show with analysis that multiple mixings or mixers show greater [whatever desired reason for a mixing to start with].
If one of the six mixers is a parrot, it doesn't matter. It ony knows that it's mixing coins for one part. Could be mixing a mixer's output and sending to a mixer's input, know your source address, or you destination address. All mixers would have to be linked parrots for there to be an issue.
Mixer analysis has already been done on most of the individual mixers. If either mixer gives a good mix, there should be no taint. The mixer knows your source and destination, if you only use one and it's compromised, there's an established link between your coins that the parrot mixer knows about.
If you were randomly using different mixers in parallel, it would be much worse than a single mixer. Series is where there is the advantage.
May 10, 2019, 10:38:14 AM
Update: This is now available in your browser. Double Bitcoin Mixer http://doublemixwcfx4wadeuvuygpxej5jpu7uleesh3yptopnbj5kshnlrid.onion/
---
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
The improvement is using two mixers, together.
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.
---
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.
Jump to: