-
Notifications
You must be signed in to change notification settings - Fork 192
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error fetching pools #1401
Comments
Ok, just read the news. Could this be caused by the whole crack down on Samourai? If so, will there be a fix for sparrow to replace the pools by another mixing service? |
Yes
I doubt it. Who would want to expose himself by running a coordinator? The government made it pretty clear that they don't want this kind of activity. This puts thousands of bitcoin users (today) and potentially millions (in the future) at risk of loosing their privacy but I guess this doesn't matter to the people in power. |
It’s a tough spot for coinjoins right now, but I’m pretty hopeful about how things could evolve. Maybe Sparrow Wallet could look into integrating something like JoinMarket instead of sticking with the Whirlpool approach? This switch could keep the essence of blockchain by keeping things decentralized and empowering users, while potentially avoiding some legal issues by not having a single point of responsibility. Integrating JoinMarket could not only sidestep current legal pressures but also enhance the resilience of the system. Does anyone else think this could be a viable path for Sparrow? |
Hi,
I keep receiving the message "Error fetching pools" when trying to mix through Whirlpool. I've read previous posts about this error and tried with Tor proxy enabled or without Tor but no success. The error keeps coming. I was wondering if there is a way to solve this problem. As a non-technical pleb, your help would be greatly appreciated.
Regards,
Reformiste
The text was updated successfully, but these errors were encountered: