WalletWasabi VS WabiSabi

When I use a search engine to find wasabi wallet, the top result is https://wasabiwallet.app/ However, on github, it says the offical site is https://wasabiwallet.io

Finally, fork Wasabi Wallet, remove what you don't need and add what you do: https://github.com/zkSNACKs/WalletWasabi

This is the list of supported operating systems https://github.com/zkSNACKs/WalletWasabi/blob/master/WalletWasabi.Documentation/WasabiCompatibility.md

For the record, this feature has been implemented already, but not released. I hope it'll make it to the next one: https://github.com/zkSNACKs/WalletWasabi/pull/10976

GitHub Discussion: https://github.com/zkSNACKs/WalletWasabi/discussions/10965

Hola. Te dejo el link al GitHub de la billetera Bitcoin 100% escrita en C# (front y back), 100% open source, en la que laburo como dev C# hace 1 año y medio aprox.

The Wasabi Wallet for Bitcoin Core, for example, manages this process almost unnoticed by the user in the background for an additional fee. The problem with this is that the system is a centralized single point of failure. State intervention cannot be ruled out. In addition, Wasabi excludes certain coins that are blacklisted, or whose origin is questionable, in order to "protect its users."

You can check its development activity on GitHub https://github.com/zkSNACKs/WalletWasabi/ if you care about that.

Not your key, not your coins. Go Non-custodial if you must. I use Wasabi Wallet mainly for the privacy.

The main difference between the two is that Wasabi is a privacy focused wallet. it is designed so that no one can breach your privacy. This is done through coinjoins, client-side block filtering and communication over the Tor anonymity network.

Check it out https://github.com/zkSNACKs/WabiSabi

All of this despite the current Tor DDoS attack which is still not yet solved, and this affects Wasabi a lot because it relies heavily on Tor, specially with the new coinjoin protocol WabiSabi that works differently than the old protocol ZeroLink, because it needs to register each input with a new Tor identity.

Have you checked the new coinjoin protocol WabiSabi which has been worked on for over two years and the amount of research and work that has been put to implement it?

If you would like to read more, Coinjoins with variable amounts

Currently not, but it will be possible with Wasabi 2.0. https://github.com/zkSNACKs/WabiSabi

I believe however that WabiSabi, which is the research we've been crafting for the past 1.5 years for Wasabi 2.0 is a better solution for the trustless coordination of arbitrary coinjoin amounts problem and I'm not trying to be disrespectful towards their solution, quite the opposite, I have great respect for that work and it certainly served as a great inspiration for us, it's just we've carefully reviewed the entire Bitcoin privacy research literature and I'd like to think we've taken the best parts out of everything. Anyhow, time will tell.