Wasabi Wallet - Total Privacy For Bitcoin

[Kruw]

That's insane. So it means not only do users have to update their Tor Browsers (which was never really a problem since the browser auto-updates itself), but every onionsite, relay and headless connector have to manually update to or compile a new Tor version. What was the reason for the mandatory upgrade? Surely, it must have been some vulnerability?

There was no vulnerability announced (yet), here is the thread where Tor contributors discussed the rollout plan: https://gitlab.torproject.org/tpo/network-health/team/-/work_items/460

[satscraper]

Surely, it must have been some vulnerability?

Not really. This is simply because Tor is in the final stage of its multi-year migration path from the C Tor codebase to new codebase^{called Arti}, which was clearly explained in their June ^23rd release. So Wasabi must follow this path in order not to lose connectivity to the network.

[FinneysTrueVision]

I saw this today on the Apple App Store. Somebody made a fake mobile version of Wasabi Wallet and put zkSNACKs as the developer to make it look legitimate. The app has reviews from months ago, which means it has been listed for a while already.

[satscraper]

I saw this today on the Apple App Store. Somebody made a fake mobile version of Wasabi Wallet and put zkSNACKs as the developer to make it look legitimate. The app has reviews from months ago, which means it has been listed for a while already.

That is why I prefer to download any wallet by following the link from its official site or repository. This prevents me from fake wallet scams.

Not everyone is aware that Wasabi (with its CoinJoin feature) is desktop-only and runs exclusively on Windows, macOS, and Linux. Scammers like to exploit any knowledge gap by creating fake mobile versions of any wallet, and your post evidences that Wasabi has had close encounters with them.

[Kruw]

I saw this today on the Apple App Store. Somebody made a fake mobile version of Wasabi Wallet and put zkSNACKs as the developer to make it look legitimate. The app has reviews from months ago, which means it has been listed for a while already.

Yes, they also have an imposter "Wasabi Wallet Mobile" X/Twitter account that has more followers than the legitimate @wasabiwallet one.

[JollyGood]

The official Wasabi Wallet website is probably getting quite a lot of traffic on a monthly basis, they should use that to their advantage by putting an alert to inform people about the fake app in the Apple store. If reviews have been left there from months ago, Wasabi Wallet really should have tried to take it down by contacting Apple.

As for the social media account, I am not sure what can be done about that but Wasabi Wallet should at least try to have it removed.

Yes, they also have an imposter "Wasabi Wallet Mobile" X/Twitter account that has more followers than the legitimate @wasabiwallet one.

[Kruw]

As for the social media account, I am not sure what can be done about that but Wasabi Wallet should at least try to have it removed.

[JollyGood]

If this is the best that Twitter/X can do when they receive reports of impersonations and scam, then I hope the website continues to lose customers. I have no idea how Twitter/X can conclude Wasabi Wallet is not being impersonated by the scammers.

What I find problematic is that it is still available on Apple Store. Maybe Apple have not received reports it is a scam app.

[Kruw]

Experimental PR for re-enabling coinjoins on Trezor hardware wallets: https://github.com/WalletWasabi/WalletWasabi/pull/14759

[Kruw]

Coordifier - A watchtower plugin for your node that continuously audits coordinators for honesty, stability, and liquidity (concept): https://github.com/orgs/WalletWasabi/discussions/14793

[satscraper]

Today Wasabi Wallet was elevated to v2.8.1. What caught my eye is that it switches new receive addresses to Taproot by default ^{five years after the soft fork activated} on the reasoning that it's time to shift upgrade pressure onto lagging wallet developers. I wonder if there are still developers out there who are uncertain about Taproot.

[Kruw]

Today Wasabi Wallet was elevated to v2.8.1. What caught my eye is that it switches new receive addresses to Taproot by default, five years after the soft fork activated, on the reasoning that it's time to shift upgrade pressure onto lagging wallet developers. I wonder if there are still developers out there who are uncertain about Taproot.

Damn, you're quick!

[lontivero]

We are proud to announce that Wasabi Wallet v2.8.1 is out. It sets a major milestone which took more than a year to achieve: to make Wasabi unstoppable.

Yes, Wasabi Wallet is unstoppable now. This is the result not only of a long, complete redesign but, even more important, of a lesson learnt from the Samourai failure. One day we all woke up with the news about the Samourai case, and what shocked me the most, apart from the human perspective, was witnessing how an open source software project can die. I remember reading users requesting support because their wallet showed them a 0 btc balance, the fear, the ignorance reigning in most of them about what that 0 meant — something I don't want Wasabi users to ever go through.

The latest version can not only work with nothing more than your own node but can also work with just the Bitcoin P2P network. Coordinators form a long chain of fallbacks, releases are distributed automatically thanks to Nostr, and even if GitHub cancels our subscription and blocks the project repo, nothing happens because Wasabi can find the releases wherever we put them.

We could enumerate features — there are lots of them — but unstoppability is the one that we would like to highlight today.

To the loyal Wasabi users, all our gratitude for your support and we hope you find this work valuable. 

[Kruw]

To the loyal Wasabi users, all our gratitude for your support and we hope you find this work valuable.  

I will never be able to repay this debt. Thank you lontivero.

The legend of Wasabi Wallet is an epic: https://www.youtube.com/watch?v=6H0vFP_jXN4

There were almost no survivors in this war. It was both a victory and a tragedy.

[Kruw]

A massive refactoring PR is now in the master branch (post v.2.8.1): https://github.com/WalletWasabi/WalletWasabi/pull/14117

Looking for testers and user feedback!

[Kruw]

BIP 77 (Async Payjoin) PRs just opened: https://github.com/WalletWasabi/WalletWasabi/pull/14875

[Kruw]

Tracking issue for removing COLDCARD support from Wasabi: https://github.com/WalletWasabi/WalletWasabi/issues/14893

Any community feedback on this topic?

[PrivacyG]

I do not know how I feel about removing Coldcard support.  Now that the support for it has been already worked on and integrated, why throw all that in the trash rather than adding a red warning instead?  So anyone who continues with out taking any measure to protect their own Bitcoin accepts the possible consequences.  Am I missing some thing other than the obvious recent tragedy?

[nc50lc]

Any community feedback on this topic?

Don't entirely remove it, for now deprecate the feature.
Just prevent users from creating a new wallet using their Coldcard while still keeping the related commands for power-users, and let Coldcard users use their existing wallet.
Then decide to entirely remove it sometime in the future.

And I strongly agree to PrivacyG's suggestion to put a striking red warning if a wallet is using Coldcard.