Wasabi Wallet - Total Privacy For Bitcoin

[Kruw]

This 1 line code change will allow users to better control UTXO consolidation by waiting for the previous coinjoin tx to get mined before registering for the next round - https://github.com/WalletWasabi/WalletWasabi/pull/13765

[Reynaldo]

 The privacy features are solid, especially that non-custodial coinjoin tech. Been using it and it's pretty smooth. Network privacy through Tor + blockchain privacy through coinjoins is exactly what BTC needs right now. Not your data, not your privacy. Watchout Winston, big brother watching you.

[JollyGood]

It seems the Wasabi Wallet team do not have any intention of slowing down. There are small but very important updates being rolled out and that is one of the best signs the project will be around for the long run. Ginger Wallet is a fork of Wasabi Wallet and as long as coinjoin software remains in demand there might be other forks in the future.

Wasabi v2.5.1 is out! Check the release notes here: https://github.com/WalletWasabi/WalletWasabi/releases/tag/v2.5.1

[Kruw]

One subtle change in the previous release was with the "Change Avoidance" feature. It now allows up to +2 additional inputs to be measured against the intended sending amount. This should make it more convenient for users who are trying to reduce their blockspace consumption.

[Kruw]

Wasabi's website is being redesigned, look out for a new skin!

[JollyGood]

It does not look significantly different from the previous version. I preferred the look before it was updated.

Wasabi's website is being redesigned, look out for a new skin!

[Kruw]

It does not look significantly different from the previous version. I preferred the look before it was updated.

The updated website isn't live yet, it's in the design process.

[JollyGood]

Unless I am mistaken, there were definitely changes to what was there previously.

It does not look significantly different from the previous version. I preferred the look before it was updated.

The updated website isn't live yet, it's in the design process.

[Kruw]

This recent PR redesigned the way Wasabi integrates with your full node, making it more standard for remote connections: https://github.com/WalletWasabi/WalletWasabi/pull/13781

[Wind_FURY]

It seems the Wasabi Wallet team do not have any intention of slowing down. There are small but very important updates being rolled out and that is one of the best signs the project will be around for the long run. Ginger Wallet is a fork of Wasabi Wallet and as long as coinjoin software remains in demand there might be other forks in the future.

Wasabi v2.5.1 is out! Check the release notes here: https://github.com/WalletWasabi/WalletWasabi/releases/tag/v2.5.1

That's actually GOOD for the fungibility of Bitcoin. In fact, as Wasabi Wallet is Open Source Software, the community, both the Bitcoin community and the Open Source community should be encouraged to fork from the original, and add their own "flavors"/changes from the original.

It will still be "Wasabi", but different.

The Linux O.S. "model" is very successful in this sort of development for software.

[JollyGood]

If the choice of adding your own coordinator is going to remain, Wasabi Wallet will continue being successful. It receives regular updates and has active contributors therefore it should have a long future.

As for forks, they will occur from time to time (such as Ginger Wallet) and they will continue to benefit by using Wasabi Wallet updates. Ginger Wallet for example imposes their own coordinator with a fee to use their service in order for them to make a profit whereas Wasabi Wallet does not. Maybe others will follow the Ginger Wallet route and create forks but will hopefully stay with the non-profit vision.

That's actually GOOD for the fungibility of Bitcoin. In fact, as Wasabi Wallet is Open Source Software, the community, both the Bitcoin community and the Open Source community should be encouraged to fork from the original, and add their own "flavors"/changes from the original.

It will still be "Wasabi", but different.

The Linux O.S. "model" is very successful in this sort of development for software.

[Wind_FURY]

If the choice of adding your own coordinator is going to remain, Wasabi Wallet will continue being successful. It receives regular updates and has active contributors therefore it should have a long future.

As for forks, they will occur from time to time (such as Ginger Wallet) and they will continue to benefit by using Wasabi Wallet updates. Ginger Wallet for example imposes their own coordinator with a fee to use their service in order for them to make a profit whereas Wasabi Wallet does not. Maybe others will follow the Ginger Wallet route and create forks but will hopefully stay with the non-profit vision.

That's actually GOOD for the fungibility of Bitcoin. In fact, as Wasabi Wallet is Open Source Software, the community, both the Bitcoin community and the Open Source community should be encouraged to fork from the original, and add their own "flavors"/changes from the original.

It will still be "Wasabi", but different.

The Linux O.S. "model" is very successful in this sort of development for software.

If you don't believe in what Ginger Wallet and other Wasabi forks are doing, then the solution is simple - Do not use them. But it's the same with other coordinators, not just Ginger Wallet, if they want to include a fee for every CoinJoin, then they should if that keeps them motivated to keep building and improving their software. They might also find bugs or improve Wasabi's code itself.

Plus it's CoinJoining as a service. I would be happy to pay for a small fee to show my appreciation. It helps that part of the community grow, and therefore helps with making Bitcoin more fungible.

[ABCbits]

Onion link: http://wasabiukrxmkdgve5kynjztuovbg43uxcbcxn6y2okcrsg7gb6jdmbad.onion/

I wanted to check old blog post, so i visit that onion link and choose "BLOG" which redirect me to https://blog.wasabiwallet.io/. But it surprise me that link show me message "403 Forbidden Access to this resource on the server is denied!". I don't mind redirection to clearnet, but i expect they configure their website to explicitly allow Tor visitor.

It seems Wasabi blog is broken again. This time i received message "SSL handshake failed Error code 525" from CloudFlare. I've tried few browser and even asked archive.org to make an archive on https://web.archive.org/web/20241107102003/https://blog.wasabiwallet.io/ with same message.

Wasabi blog page is broken problem again. This time, my browser simply says "Hmm. We’re having trouble finding that site. We can’t connect to the server at blog.wasabiwallet.io.". I had to share archive link on different post, rather than direct link.

[JollyGood]

I did not state what my belief was however I encourage forks of any open source software as it is the innovation part that is going to take the code forward.

My post had no negative connotations towards either Ginger Wallet or Wasabi Wallet. If developers fork the code and force clients to pay a coinjoin fee that is their prerogative.

Having said that, if I had to choose between the two, it would be Wasabi Wallet but that does not negate anything Ginger Wallet has contributed.

If you don't believe in what Ginger Wallet and other Wasabi forks are doing, then the solution is simple - Do not use them. But it's the same with other coordinators, not just Ginger Wallet, if they want to include a fee for every CoinJoin, then they should if that keeps them motivated to keep building and improving their software. The might also find bugs or improve Wasabi's code itself.

Plus it's CoinJoining as a service. I would be happy to pay for a small fee to show my appreciation. It helps that part of the community grow, and therefore helps with making Bitcoin more fungible.

[Wind_FURY]

I did not state what my belief was however I encourage forks of any open source software as it is the innovation part that is going to take the code forward.

My post had no negative connotations towards either Ginger Wallet or Wasabi Wallet. If developers fork the code and force clients to pay a coinjoin fee that is their prerogative.

Having said that, if I had to choose between the two, it would be Wasabi Wallet but that does not negate anything Ginger Wallet has contributed.

If you don't believe in what Ginger Wallet and other Wasabi forks are doing, then the solution is simple - Do not use them. But it's the same with other coordinators, not just Ginger Wallet, if they want to include a fee for every CoinJoin, then they should if that keeps them motivated to keep building and improving their software. The might also find bugs or improve Wasabi's code itself.

Plus it's CoinJoining as a service. I would be happy to pay for a small fee to show my appreciation. It helps that part of the community grow, and therefore helps with making Bitcoin more fungible.

OK, your argument/debate is understandable, but everyone should also understand that open source developers should be incentivized to continue building. But they can also choose to contribute for free during their spare time if that's the path they choose.

It's like Linux. Linus Torvalds and other open source contributors built and continues to develop the Linux kernel FOR FREE. There are other developers that build they're own "flavor" of Linux that they distribute for free like Slackware, BUT there are others like Red Hat that builds their own flavor for a fee/payment. It's merely a path to be incentivized. It will be the users' choice if he/she wants to accept the trade-off for the paid service.

[Kruw]

Wasabi blog page is broken problem again. This time, my browser simply says "Hmm. We’re having trouble finding that site. We can’t connect to the server at blog.wasabiwallet.io.". I had to share archive link on different post, rather than direct link.

Sorry about the dead links, Wasabi's website is still being redesigned (I'm not involved, so I have no idea when it will be finished).

Wasabi's website is being redesigned, look out for a new skin!

[ABCbits]

Wasabi blog page is broken problem again. This time, my browser simply says "Hmm. We’re having trouble finding that site. We can’t connect to the server at blog.wasabiwallet.io.". I had to share archive link on different post, rather than direct link.

Sorry about the dead links, Wasabi's website is still being redesigned (I'm not involved, so I have no idea when it will be finished).

Wasabi's website is being redesigned, look out for a new skin!

I see. But i don't see correlation between how website being redisgned and dead link/blog, unless they directly use production server/domain rather than testing ones.

[JollyGood]

There have to be some form of incentives to keep developers involved with pushing out regular updates. In many cases donations and tips are simply, not enough therefore adding a revenue streams makes complete sense. Not all developers are able to commit to the open source route. The Linux flavours you cited gave are good examples of when paid software works.

If Wasabi Wallet is forked by others that want to make money from it for providing services, I see it as a step forward as overall it adds to the group of options.

OK, your argument/debate is understandable, but everyone should also understand that open source developers should be incentivized to continue building. But they can also choose to contribute for free during their spare time if that's the path they choose.

It's like Linux. Linus Torvalds and other open source contributors built and continues to develop the Linux kernel FOR FREE. There are other developers that build they're own "flavor" of Linux that they distribute for free like Slackware, BUT there are others like Red Hat that builds their own flavor for a fee/payment. It's merely a path to be incentivized. It will be the users' choice if he/she wants to accept the trade-off for the paid service.

[Kruw]

I see. But i don't see correlation between how website being redesigned and dead link/blog, unless they directly use production server/domain rather than testing ones.

The blog was hosted on a separate server, so its content is no longer available.

[Wind_FURY]

For those users who are very active in CoinJoins, I believe it's better to stop and wait after everything settles down, because there are Bitcoins being traced related to the ByBit hack.

We have debated over this many times before, but just to avoid any problems, don't risk tainting your outputs.

But precisely this happened over the past couple of days. Turns out ByBit Hack related funds are moving through different Bitcoin rails and caused funds to be flagged and frozen by different regulated exchanges. To counter this, we added the ByBit blacklist (https://dt074px2e9qbh.cloudfront.net/exploit-api.json) in addition to the OFAC blacklist. Goes without saying, that checks against these lists run locally on our server.

So... we are not blocking Bitcoin originating from coinjoins, but if you are participating in a coinjoin round with blacklisted ByBit Hack addresses, then we do. If you intend to use Boltz with coinjoined funds, it's a good idea to investigate about your coordinator a bit beforehand

https://stacker.news/items/926959