Wasabi Wallet

🚨 New release 2.7.0 is here 🚨 2.7.0 is a stabilization update that boosts reliability while bringing a fresh look & smoother performance 🟠 Enhanced Node Integration 🎨 Refreshed UI ⚙️ 1 Config/Network 🤯 Smarter Coordinators Release Notes & Download github.com/WalletWasabi/W…

@Yashraj__ > Any plans to support BIP-77 async payjoin? No direct plan but if external contributors wants to build support we can help > how do you feel about letting users “save” silent payment addreses for future, since they can be reused?? Really good idea!

Very cool communication & subtle marketing @wasabiwallet Question: - is Payjoin support BIP-78 only? Any plans to support BIP-77 async payjoin? - how do you feel about letting users “save” silent payment addreses for future, since they can be reused??

We released Wasabi v2.7.2 is out with a couple of bug fixes. See changelog github.com/WalletWasabi/W…

Peter Todd @peterktodd just released his report on Coinjoin privacy ahead of his talk at our event in Riga next week where he'll be speaking about it (link in next post) Is there a flaw in Wasabi's privacy model? Peter digs into common privacy heuristics and gives an overview of each of the major implementations

Sparrow doesn't *require* it but strongly pushes for it, and works much better that way. Specter Desktop allowed for both but is basically dead. Wasabi and Fully Noded might be the only two wallets I know of that work by directly connecting to a Bitcoin node.

For the record, Wasabi always used Custom Block Filters, not directly BIP158. v2.6.0 makes it possible to sync with filters created by a Bitcoin Node, and therefore sync exclusively with it. On synchronization time, it is not as big of a problem as you might think, and well done (not yet the case in Wasabi) can provide a user experience close to privacy-harming sync mechanisms, especially for newish and smallish wallets (where UX is the most important)

Version 2.6.0 of @wasabiwallet adds BIP158 block filters, and now syncs via BIP158 without a backend indexer. A big move for privacy-focused users. @nvk , @craigraw , Odell and @Rob1Ham discuss the update in BR096.

If you use Wasabi with your own node, please make sure that you are running Wasabi v2.6.0. Previous versions are affected by an issue that makes the client unable to process blocks 896727 and 897389 Clients running v2.6.0 or not connected to a specific node are not affected.

@onwaybitcoin Wait no more! github.com/remcoros/wasab… Thanks @remcoros

Loads fast? This page weighs 125 kb... A whopping 156x less than the previous version. It also uses no javascript!

New skin for the website wasabiwallet.io 👀

Added Shamir Backup/Import support to our Software Wallets comparison. @bluewalletio @ElectrumWallet @SparrowWallet @wasabiwallet thebitcoinhole.com/software-walle…

🤯 And more… - Updated Avalonia to v11.2.7 - Added a configurable third-party fallback for broadcasting TXs - Rebuilt all JSON Serialization mechanisms (now Stricter) - Changed our Windows Code Signing Certificate, now using Azure Trusted Signing Etc...

💪 Nostr Update Manager We're introducing a cutting-edge mechanism using the censorship-resistant Nostr network to receive update information and download locations instead of relying on GitHub's goodwill.

🚨 New release 2.6.0 - Prometheus is here! 💥 Support for Standard BIP 158 Block Filters 💻 Full Node Integration Rework 🔐 Create & Recover SLIP 39 Shares 💪 Nostr Update Manager And more… github.com/WalletWasabi/W…

Several times @benbybit referred to Wasabi as a mixer, and no change has been made despite our requests: Wasabi is a... wallet. Wasabi can act as a client for the WabiSabi Multi-Party Tx Protocol, users can then connect to any third-party coordinators, not related to Wasabi.

@benbybit Wasabi is not a mixer. It's a wallet that has an implementation of a trustless multi-party transaction protocol, coordinated by third-parties. In the same way Sparrow used to implement another coinjoin protocol not operated by Sparrow themselves.

3.20.25 Executive Summary on Hacked Funds: Hacker started to use mixers: 1. Wasbi 2. CryptoMixer 3. Railgun 4. TornadoCash Total hacked funds of USD 1.4bn around 500k ETH. 88.87% remain traceable, 7.59% have gone dark, 3.54% have been frozen. Breakdown: - 86.29% (440,091 ETH, ~$1.23B) have been converted into 12,836 BTC across 9,117 wallets (Average 1.41 BTC each). We notice that Hacker started to use BTC mixer. 193 BTC went to mainly Wasabi Mixer. After mixer the funds went to various p2p vendors. We believe this trend will grow as more funds will go through mixers. Decoding mixer transactions is the no.1 challenge we face now. If you can help, please reach out. In the past 30 days, 5012 bounty reports were received of which 63 were valid bounty reports. We welcome more reports, we need more bounty hunters that can decode mixers as we need a lot of help there down the road. For more real time update, visit lazarusbounty.com

@its_Johnnyb0ii #send-bitcoins-from-cold-wasabi" target="_blank" rel="nofollow noopener">docs.wasabiwallet.io/using-wasabi/C… #can-i-import-a-watch-only-extended-public-key" target="_blank" rel="nofollow noopener">docs.wasabiwallet.io/FAQ/FAQ-UseWas… (Note that if you use this workflow you should use null for TaprootExtPubKey if your cold wallet doesn't support taproot)

@wasabiwallet Just downloaded Wasabi to give it a try but was disappointed it doesn't natively let importing a watch-only wallet. How do I use an airgapped HW to transact through Wasabi?

🚨 New release 2.5.0 is here! 💪 3rd Party Providers for Fee & Exchange Rate 👨‍🔧 Quality of Life Features 📦 Backend and Coordinator packaged for Linux This version continues to improve resiliency and makes some long-awaited improvements as a thank-you to our community!