Hello, Who can advise working, proven Ethereum mixers. Except for the tornado.

Another mixer closes the doors. Removing Foxmixer.com.

If you visit the website there is an empty page with a message claiming the service has been seized. True or not, it doesn't matter a lot but usually when a domain is seized there is a more explicit template about it, with a message from who/what, according to X or Y.
It seems like a fake page to me, to exit the business with a valuable excuse. There is nothing wrong if your business doesn't work, mistakes happen to everyone.

the code show nothing more than

Could you let us know which two mixers you tried but didn't work? This would be helpful for other members to avoid the same mistakes.


Yes.

Is this a serious question? If anyone in this world has tried bitcoin mixer, definitely it was Chipmixer. It's the most known and reputable mixer out there.

Hi,

Can someone who has used one that works recommend me a Mixer that does work? I have tried 2 and neither have worked.
Has anyone tried ChipMixer?
thanks

I just found false crypto mixers

the-crypto-mixer.org
tether-mixer-anonymous.org
ethereum-mixer-eth-mixer.com
eth-ethereum-mixer.org
ether-mixer.org
eth-mixer.org
ethereum-mixer-anonymous.org
best-ethereum-mixer.org
bitcoinlaundry.online
bitcoin-laundry.mx
bitcoinlaundry.org
bitmix.it
bitmixbiz.com
bitmixr.biz
bitsmix.biz
bitmixbiz.com
veio.io

All appear on bing

Wasabi starts blocking certain transactions to its CoinJoin mixing protocol. Crazy but true.

I'm totally disappointed by their move and a large setback. The "certain transactions" are not defined but since it was done to protect their company from hackers and scammers' funds (as they say), we can have a guess but who knows how deep they go. They may end up with a partnership with Elliptic, Chainanalysis and co.  
If they were not under a company, they wouldn't need to take such action that we could name censorship.

As of now, the zkSNACKs coordinator will start refusing someUTXOs from registering to coinjoins. Either you switch to joinmarket or run the coordinator and configure wasabi for you., I don't know, but I'm sure I have never see a mixer with such acts

Cloudflare is a private company. I know they are offering tons of bells and whistles, and they keep adding to their portfolio on a regular basis. To much to keep up for me anyways.
But the features you seem to be reffering to is their feature to upload your own certs and keys, and the feature for keyless ssl?
I never used these features, but i looked them up for a discussion i had a long time ago, so i'm aware of their technicality's. If i remember correctly (i didn't re-read the whitepaper, this stuff comes from memory) the first feature gives cloudflare all the tools to generate symmetric keys themselves, the other just gives them only the symmetric keys (and you host some kind of service on your host to let them request a new symmetric key).
These service *might* look "better" to the untrained eye, but in fact they are worse: when you use them you're even hiding the fact that cloudflare acts as a MITM (but they still are!!!). When you use these services, your customers will never know cloudflare can (and will!!!) decrypt every package they exchange.

The bottom line is very, very simple and does not differ from which package you buy or which technology they implement: their proxy REQUIRES them to decrypt the traffic between (what the visitor thinks is) the visitor and the webhost.
Why? Well, you know those nice features they offer: DDos protection and their CDN? Both these things are built on the fact that they keep a big cache of DECRYPTED data from YOUR host on their datacenters. When a client requests a page, they HAVE to be able to see what the client requested (so they HAVE to decrypt the request), then they can see if they have the requested data somewhere on their servers (UNENCRYPTED). When they don't have the data in their cache, they WANT the data in their cache, so they request it from the host, DECRYPT it, and PUT it in their cache before (or after) re-encrypting it and sending it to your client.

That's why they're able to offer DDos protection: your data is on so many geo-located servers, and they're so big, an attacker just can't muster up a botnet that's so big he/she can tear down cloudflare. They'r still DDos'ing, cloudflare does not stop them, cloudflare just absorbs the requests... Maybe they block them after a while, IDK, but in the first place they just absorb them due to the fact they have your data anyways, and they have dozens of copy's of your data all around the world, so let a botnet request a couple million of copy's: they don't care.

That's why they can speed up your site: they have copy's of most of your content all over the world on fast servers: a client downloads most of your content directly from cloudflare (and not from you), from a fast server close-by.

And in the end it doesn't matter if you use cloudflare's SSL, you upload your cert+key or you run "keyless ssl" by running a local deamon to generate symmetric keys.... If you use the proxy, they have your data.... Which is bad for a mixer.

And the thing is (and i've said this before): i wouldn't even mind all that much if the mixer operators had any clue as to what they were doing and warned their clients... Like @LeGaulois already said: some people won't care if law enforcement knows who they are, they just want $5 wrench protection.
But the very least a mixer operator should do is plaster a big warning on their clearnet site about the fact that the clearnet version is cached by cloudflare and both cloudflare employees and law enforcement. At least this would demonstrate the fact the mixer operator knows enough about this techology to run a mixer.

But by acting like most mixer operators do when i point out they use cloudflare (shrugging, telling me other do the same thing), i get scared.... Very scared.... How can you trust the algorithm, the code, the workflow of a mixer operator who doesn't understand the slightest thing about why a MITM is bad for a mixer? When i see the reactions from mixer operators, i always wonder what their code would look like.... Or maybe they're running their operation from shared hosting? Or maybe.... Well horror scenario's pop to mind....

Maybe you didn’t quite understand me. I meant that the problem with ssl certificates is even more interesting than it seems.

For example, if I register for cloudflare and pay a $10 tariff, my certificate will be visible to everyone as an outsider. And if I pay $200, I can download any certificate, but the private key is still on cloudflare. And I can order private DNS. How carefully you examine the site before visiting it.

I see your point of view... And i do agree... You're in a grey area yourself, you're not really a mixer, so maybe you can get away with using cloudflare's SSL certificates... This being said: three letter agencies might still find it usefull to know who your partners are, so i wonder if it wouldn't be better to use an x3 certificate instead of cloudflare's. Offcourse, you'd lose DDos protection, your website responsiveness *might* drop (if you were using slow hosting, or a high latency dc), and you'd use a little bit more bandwith.

I actually pointed this out to you in august 2018!
https://bitcointalksearch.org/topic/m.44815063

Here's your reply:

At this moment, your platform is enabling 7 mixing services (when looking at https:  //    jambler.io /mix -coins.  php). 6 have a clearnet presence, 3 of them use cloudflare, and one does not use ssl at all (what?). I know there are your customers, but maybe giving them a nudge in the right direction wouldn't be to bad? Only 3 out of 7 of your clients got it right... Some kind of guidance from you side would probably be a good thing for privacy as a whole.

@LeGaulois: you make a valid point aswell... For some people, "moderate" privacy against non-law enforcement might be enough... I know i have never actually needed protection against the law, i'd still like them to keep their nose out of my business tough
The main problem, which is the same for cloudflare SSL certificates and tor: not everybody is tech savvy, not everybody will do their homework... A lot of people will just use google to find a mixer, look at the green padlock, read the promo text and mix their coins, thinking they are now anonymous... A lot of people won't look at which certificate is issues by who, they won't look up nameservers or dns records, they won't inspect the code for embedded javascript,... They certainly won't download the tor proxy and start using the tor mirror... They are average people that want privacy, they trust the mixer in question, and in the end, they usually don't get the privacy they payed for... Granted, 99% of them don't *need* said privacy, they still payed for it, they  trusted the mixer, so they should get that privacy (wether they need it or not).

But that's just my opinion

That doesn't matter: the certificate handles the traffic between the user and Cloudflare, not between Cloudflare and the server. See this post (about Bitcointalk, but it applies to any site that uses Cloudflare):
Or my own (layman) explanation: Cloudflare can only stop DDOS if they know what traffic is coming in. In order to stop only the attack and not all data, Cloudflare has to decrypt everything.

I understand part of your concern. And it would be interesting to hear your opinion. For example, the site may have a certificate issued by an outside organization, but it will still use cloudflare services, you will never know, but you will be sure of your safety.

And I’d like to point out one thing. Jambler, for example, is not a mixer, it’s a platform for the rapid deployment of mixers. The end-user who does not want to advertise the sending and receiving addresses and other data does not address to the site jambler, and not mediocre to our partners. Also, all default partners have a version of tor that helps raise the level of anonymity.

Any data that gets recorded can get leaked. I'm not sure how secure 3 letter agencies are, but I am sure they can't leak what they don't know.

Don't worry, I have no problem with that. It's all about debate and I like doing it

And to be honest, I don't have another argument to put on the table, but just something about



Some people don't care about law enforcement that might be able to obtain data. For example, I pay a prostitute, I have no problem if a 3 letter agency knows it. what they could do with that? Asking me if the pussy was good.?

they go to the category

I know i'm preaching to the choir here, and i know this is your thread, but i still wanted to chip in to give some more background information since i think this is really, really important stuff...

I've actually dedicated a complete thread to this problem, i like to refer to it since it cost me a long time to write this stuff up: https://bitcointalksearch.org/topic/mixers-using-cloudflares-ssl-certificates-5247838

The problem with the soup analogy is the following.
When i eat soup, i have several "mayor" goals and a couple "minor" goals.

• I want nourishment: mayor goal
• I want a healthy snack: mayor goal
• I want something to quench my thirst: minor goal
• I want something warm: minor goal

If mixers using cloudflare had to fit into the soup metaphore, cloudflare mixers would be like calling hot water with salt "soup". When it comes to my goals:

• I want nourishment: mayor goal: FAILED
• I want a healthy snack: mayor goal; FAILED
• I want something to quench my thirst: minor goal: OK
• I want something warm: minor goal: OK

When it comes to mixing, i also have mayor and minor goals... When talking about cloudflare mixers, this is where i stand:

• I want complete anonymity against everybody (including law enforcement): mayor goal: FAILED
• I want "normal" (non hacker/non law enforcement) users not to be able to track me: minor goal: OK

The problem here is that, once a site uses cloudflare's SSL certificates, what happens is:
The mixing client creates a symmetric key between their device and CLOUDFLARE... The user THINKS he's safe because he/she sees a green padlock in the mixer's url, but he does not realise cloudflare WILL decrypt EVERY package they sent to (what they think is) the mixer. Cloudflare then looks at the requests, checks it's cache, and if the request cannot be fetched from the cache, they create a symmetric key between cloudflare and the mixer to request the missing content.

This means that, when a mixer uses cloudflare, cloudflare will know:

• The exact deposit address shown by the mixer
• The exact withdrawal address entered by the client
• The letter of guarantee (if the client downloads it)
• The client's ip
• The client's browser fingerprint
• The exact timestamp

Not only this, but cloudflare is a US company... In the US, data privacy seems to stop as soon as law enforcement comes into play... This basically means that, if you use a mixer using cloudflare, law enforcement *might* be able to obtain more data about you than if they'd had access to your wallets directly.

Now, once again: i'm not against cloudflare... Cloudflare protects even my own blog against DDos attacks, it speeds up my site due to their cache, it lets me enhance my site due to their addons, it handles my emails, it's a really easy dns record editor,.... Cloudflare is great, as long as your visitors don't have anything to hide from a US company (and US law enforcement).

It's great for non-political blogs, it's great for mom and pop shops... This being said: it's not OK to use cloudflare's cache (and their ssl certificates) for a mixer, a gunshop, a political blog, a porn site,...

Sorry for the delay , i deleted facebook twitter , and reddit, but mixsafer website is fully operational, like jambler.io platform. If you wanna contact https://mixsafer.com o https://jambler.io team ,please , you can use telegram , we will re-open social networks, but for now, telegram is fine https://t.me/mixsafer, or jambler group https://t.me/jambler
Jambler platform is working fine

While I agree with your view and have the same speech here and there, it's hard to say a mixer isn't a mixer due to its setup. It's like arguing your soup isn't a real soup because you haven't followed the highest standards. At best, we could argue about a blender not using the appropriate methods, but it's up to people to make their own opinion/searches about what's good and what's not

It is about lowering risk, hiding with SSL, the problem is it increases another one. It's not easy to judge the pros and cons to find the right ratio.

And about SSL, I wonder why CF is so prominent (even on the web in general) when there is a multitude of alternatives. CF is really a big fish

(I will edit the OP during the weekend)

Eventough i think jambler.io has no place between mixers in the first place due to their MITM integration of cloudflare (nor do i think any other "mixer" using cloudflare's SSL certificates should be called a mixer, maybe a "semi-obfusicator" would be a better term) , it does seem like the owner has updated his thread for the first time in a very long time:
https://bitcointalksearch.org/topic/m.59095552

All mixers using jambler.io look inactive and abandoned. As for mixsafer.com, I noticed they deleted their Facebook page and their Reddit account and it was done not long ago because I was able to see the content via google web cache. But at the same time, they used Twitter last month. They display jambler.io's email on their website to make things on autopilot for the support (i guess). Whatever but the service doesn't seem active for now

This weekend, I tried to email jambler.io but it wasn't delivered, look like they deleted their email

Time to remove mixsafer.com

edit:

Bitcoin mixers using jambler.io include:
- XXL Mixer
- Bitmixer.online
- Mixer1.money
- Mixtum
- Bitmixer.cash
- Mixtura.money
- Mixsafer.com

I also propose to remove from the list mixsafer.com, they also use the platform jambler.io, their mail ([email protected]) does not work, the topic is inactive