Post
Topic
Board Wallet software
Merits 4 from 1 user
Re: Whirlpool surge cycles (Samourai/Sparrow)
by
RickDeckard
on 03/06/2023, 22:01:04 UTC
⭐ Merited by o_e_l_e_o (4)
The best method is to set up and use JoinMarket - https://github.com/JoinMarket-Org/joinmarket-clientserver

You run the software yourself via your own node, connect to other users in a peer to peer manner over Tor, and there is no centralized coordinator. It also gives you the most options in terms of customizing your fees, size of your coinjoins, size of your outputs, and so on. It is the best coinjoin implementation at present. However, it is also the most technical to set up and use. There are very good guides on their GitHub, and I have no doubt that a technically minded user such as yourself would be able to get it set up and running, but it will take a bit of time and work to do so.
Wasn't aware of this project, seems interesting! I've checked their GitHub and it has a ton of information, I'll have to invest some time in trying to make sure that I set it up correctly. Thank you for that! Have you been using it for a while? Could you share some feedback?
The other option is using Samourai's Whirlpool, as is being discussed in this thread. Whirlpool does use a central coordinator, so it is absolutely vital that you use it with your own node and Tor to keep your privacy from the central coordinator. Your best options at the moment for connecting to Whirlpool are either Samourai wallet on mobile or Sparrow wallet on desktop. There are some other wallets starting to develop Whirlpool access as well, but I haven't tried or reviewed them so I won't recommend them. Again, there are good guides and both wallets provide a nice friendly GUI so they are much easier to set up and use than JoinMarket.
If JoinMarket proves to be way to technical for me I guess I'll end up using either of those. Sparrow seems a balanced option and after a quick Google search I managed to find good guides in using Whirlpool with it, so if everything fails, this would be a nice 2nd option.
Regardless of which one you choose, I would spend some time reading about that specific implementation works, how it handles things like toxic change, and the steps you need to take to not mess up and negate the privacy it provides.
At the end of the day this is what concerns me (fully understand what's the concept behind the implementation), so I guess it will take some time before I run any coinjoins. The path is more clear to me however, so thank you for that.