Hi everyone.
It seemed no one was using this for quite some time, or at least for any sizeable amount of funds where I've noticed any commissions. At one point it was definitely being used for some large transfers and I never heard of any issues.
Unfortunately, I haven't been running the .onion for a while now, but the code is all still there. I've been busy working on other things. I'd like to hand the reins over for the Github organization and the private key for the .onion.
I could try to sell it to the highest bidder, but then I'd worry about a scammer getting it. So make me an offer of compelling words, Bitcoin, both, or neither, and maybe I'll send it your way for someone else to continue with. Strongly prefer someone with a good track record and who's savvy.
The code is all open source of course if you just want to launch the same thing, rebranded: https://github.com/doublemixer/
I also have the doublemixer-python project and associated libraries that I can transfer into the organization first (and make sure it's transfered from Pypi).
Topic: Double Mixer: Mix your Bitcoin with two mixers in series (Read 1466 times)
...
Great project, sega01
There is a case to be made for mixing two different ways if you're going to mix twice. It might be very hard, but running BTC through Wasabi (CoinJoin) and another mixer might (perhaps Wasabi first?) be very difficult for analysts to break.
Writing the code might be hard though.
Great project, sega01
There is a case to be made for mixing two different ways if you're going to mix twice. It might be very hard, but running BTC through Wasabi (CoinJoin) and another mixer might (perhaps Wasabi first?) be very difficult for analysts to break.
Writing the code might be hard though.
Thank you!
I don't think Coinjoin or Wasabi could be easily integrated into a browser, especially without some kind of proxy layer. But I agree, two different types of mixing would be preferable.
Hopefully the mixing methods used here are dissimilar enough.
Hi everyone.
It seemed no one was using this for quite some time, or at least for any sizeable amount of funds where I've noticed any commissions. At one point it was definitely being used for some large transfers and I never heard of any issues.
It seemed no one was using this for quite some time, or at least for any sizeable amount of funds where I've noticed any commissions. At one point it was definitely being used for some large transfers and I never heard of any issues.
Thanks for your work on this project! It definitely brought some cool new ideas to bitcoin mixing and the fact it is open source makes it still useful for everyone interested.
I'd vote for keeping your bitcoin affiliate address in at least one of the mixer stages to whoever is going to take it over.
~
It it wasn't made with Python, I would love to take over and even implement ChipMixer's API as the final step (Mix > Mix? > CM chips). Unforunately, I don't really know any about it besides the very basic. 
That was a really cool project. Thanks for that.
I checked the site of this tumbler. Its nice and easy. Great job done, as far as designing the interface is concerned.
Are there any reviews of clients who have used this service and there experience? I went through thread and wasn't able to find any.
Are there any reviews of clients who have used this service and there experience? I went through thread and wasn't able to find any.
Seems different with other version minxer 
...
Great project, sega01
There is a case to be made for mixing two different ways if you're going to mix twice. It might be very hard, but running BTC through Wasabi (CoinJoin) and another mixer might (perhaps Wasabi first?) be very difficult for analysts to break.
Writing the code might be hard though.
Great project, sega01
There is a case to be made for mixing two different ways if you're going to mix twice. It might be very hard, but running BTC through Wasabi (CoinJoin) and another mixer might (perhaps Wasabi first?) be very difficult for analysts to break.
Writing the code might be hard though.
Question though- Is there anyway to calculate the fees of the mixing before we start mixing (I haven't tried this yet, asking before I do anything) Thanks for making this, much love.
Not an already calculated value/overview, but you can just read the Letters of Guarantee before sending anything. In my just generated example case:Quote
Receiving Mix Letter Of Guarantee
[...] Our fee is 3.761% + 0.0003 for every forward address
Final Mix Letter Of Guarantee
[...] A total transaction fee of only 1 % and a fee of 0.00100000 BTC per payout address is subtracted.
[...] Our fee is 3.761% + 0.0003 for every forward address
Final Mix Letter Of Guarantee
[...] A total transaction fee of only 1 % and a fee of 0.00100000 BTC per payout address is subtracted.
Then you need to manually calculate that.
Considering that the letter's format is always the same (supposedly), maybe he could scrape these percentages and make a calculator.
Ah, got it. I probably should've just went to the next stage of mixing to find out, but I guess I was a tad lazy. Thanks
Question though- Is there anyway to calculate the fees of the mixing before we start mixing (I haven't tried this yet, asking before I do anything) Thanks for making this, much love.
Not an already calculated value/overview, but you can just read the Letters of Guarantee before sending anything. In my just generated example case:Quote
Receiving Mix Letter Of Guarantee
[...] Our fee is 3.761% + 0.0003 for every forward address
Final Mix Letter Of Guarantee
[...] A total transaction fee of only 1 % and a fee of 0.00100000 BTC per payout address is subtracted.
[...] Our fee is 3.761% + 0.0003 for every forward address
Final Mix Letter Of Guarantee
[...] A total transaction fee of only 1 % and a fee of 0.00100000 BTC per payout address is subtracted.
Then you need to manually calculate that.
Considering that the letter's format is always the same (supposedly), maybe he could scrape these percentages and make a calculator.
Unsure why it took me this long to find something like this, probably wasn't looking hard enough.
+Merited.
Question though- Is there anyway to calculate the fees of the mixing before we start mixing (I haven't tried this yet, asking before I do anything) Thanks for making this, much love.
+Merited.
Question though- Is there anyway to calculate the fees of the mixing before we start mixing (I haven't tried this yet, asking before I do anything) Thanks for making this, much love.
Tor Browser 9 issue has been worked around. The canvas bug where you couldn't see QR codes on Tor Browser has also been fixed by switching to an HTML table based QR generator.
So back in business
.
Clearnet double mixer
Tor double mixer
So back in business
.Clearnet double mixer
Tor double mixer
Two mixers are always better than only one
Code:
The receiving mixer stage is broken in Tor Browser 9 when using the doublemix....onion Hidden Service.
what the mean is that?
Normally:
1. You send BTC to receiving mix.
2. Receiving mix send BTC to final mix.
3. Final mix sends BTC to your output address.
With this issue:
1. You send BTC to final mix.
2. Final mix sends BTC to your output address.
1 Less step.
I appreciate your reply. If you do that, there's no reason to use DoubleMixer as it would just be a single mix.
Hopefully the bug will be fixed though. If you're not on Tor Browser 9 you should be okay. You can also use the clearnet site (https://doublemixer.github.io) from Tor Browser and it will work fine.
Bug report is here: https://trac.torproject.org/projects/tor/ticket/32255
I'm working with Bitmix to see if we can find a workaround.
Code:
The receiving mixer stage is broken in Tor Browser 9 when using the doublemix....onion Hidden Service.
what the mean is that?
Normally:
1. You send BTC to receiving mix.
2. Receiving mix send BTC to final mix.
3. Final mix sends BTC to your output address.
With this issue:
1. You send BTC to final mix.
2. Final mix sends BTC to your output address.
1 Less step.
Code:
The receiving mixer stage is broken in Tor Browser 9 when using the doublemix....onion Hidden Service.
what the mean is that?
I'd like to announce an affiliate / referral program for Double Mixer.
It's very straight forward. Just send people to:
and/or:
For more information, see here. There's even a referral URL generator to make things easier.
It's very straight forward. Just send people to:
Code:
https://doublemixer.github.io/#ref=(your bitcoin address)
and/or:
Code:
http://doublemixwcfx4wadeuvuygpxej5jpu7uleesh3yptopnbj5kshnlrid.onion/#ref=(your bitcoin address)
For more information, see here. There's even a referral URL generator to make things easier.
Hi!
I'm what you could call a power-user of FoxMixer (used various others before).
By chance I stumbled across your project while browsing through this forum and I decided to have a closer look.
I'm not a programmer so I like that it'S damn simple to just enter the address and boom: everything else is done for you and the letters of guarantees are downloaded. Good job!
It's not that I will now always use two mixers but it's good to have the choice.
Just wondering why this project is so hidden. This should also be featured on other bitcoin sites IMHO. - Excellent work!
I'm what you could call a power-user of FoxMixer (used various others before).
By chance I stumbled across your project while browsing through this forum and I decided to have a closer look.
I'm not a programmer so I like that it'S damn simple to just enter the address and boom: everything else is done for you and the letters of guarantees are downloaded. Good job!
It's not that I will now always use two mixers but it's good to have the choice.
Just wondering why this project is so hidden. This should also be featured on other bitcoin sites IMHO. - Excellent work!
Yeah, FoxMixer is pretty great. I've found their team to be extremely responsive getting back to me. BitMix has also been responsive, helps earn trust that way for sure.
Agreed, double mixing is often overkill, I just wanted to make it a bit easier and have more discussion of the concepts. It's kind of a working proof of concept.
Thank you!! I very much appreciate what you said.
Hi!
I'm what you could call a power-user of FoxMixer (used various others before).
By chance I stumbled across your project while browsing through this forum and I decided to have a closer look.
I'm not a programmer so I like that it'S damn simple to just enter the address and boom: everything else is done for you and the letters of guarantees are downloaded. Good job!
It's not that I will now always use two mixers but it's good to have the choice.
Just wondering why this project is so hidden. This should also be featured on other bitcoin sites IMHO. - Excellent work!
I'm what you could call a power-user of FoxMixer (used various others before).
By chance I stumbled across your project while browsing through this forum and I decided to have a closer look.
I'm not a programmer so I like that it'S damn simple to just enter the address and boom: everything else is done for you and the letters of guarantees are downloaded. Good job!
It's not that I will now always use two mixers but it's good to have the choice.
Just wondering why this project is so hidden. This should also be featured on other bitcoin sites IMHO. - Excellent work!
Alright, finally got this done!
https://doublemixer.github.io
http://doublemixwcfx4wadeuvuygpxej5jpu7uleesh3yptopnbj5kshnlrid.onion/
Live with double mixing. Please let me know how it works out for you. Obviously, please audit the code, make sure you don't send too much or too little (read the minimums/maximums in the guarantees), validate the signatures, etc.
Thanks for BitMix and for Foxmixer for both enabling CORS headers to make this possible.
If you connect to the .onion, the upstream mixer's .onions will be used for connecting to their API. If you use clearnet, that's obviously not the case.
Lastly, one major update on doublemixer-python. It now uses a local Tor SOCKS proxy and the corresponding Hidden Services by default.
https://doublemixer.github.io
http://doublemixwcfx4wadeuvuygpxej5jpu7uleesh3yptopnbj5kshnlrid.onion/
Live with double mixing. Please let me know how it works out for you. Obviously, please audit the code, make sure you don't send too much or too little (read the minimums/maximums in the guarantees), validate the signatures, etc.
Thanks for BitMix and for Foxmixer for both enabling CORS headers to make this possible.
If you connect to the .onion, the upstream mixer's .onions will be used for connecting to their API. If you use clearnet, that's obviously not the case.
Lastly, one major update on doublemixer-python. It now uses a local Tor SOCKS proxy and the corresponding Hidden Services by default.
Making some progress on the Javascript version. Currently only FoxMixer is used, so it's a single mixer and no better than using Fox Mixer directly. But, hoping to add BitMix soon.
https://doublemixer.github.io
http://doublemixwcfx4wadeuvuygpxej5jpu7uleesh3yptopnbj5kshnlrid.onion/
https://doublemixer.github.io
http://doublemixwcfx4wadeuvuygpxej5jpu7uleesh3yptopnbj5kshnlrid.onion/
Jump to: