That’s a good question, but this isn’t actually a new risk unique to Nostr. Any software distribution channel depends on some account or key. If an attacker gained access to GitHub maintainers’ accounts, or to DNS records, the outcome could be the same. Nostr doesn’t make this problem worse... it just changes the medium.

More importantly, Wasabi doesn’t auto-update. The client only notifies users that an update is available. Before any update is accepted, the client independently checks that the binaries are signed with our official PGP key, which is bundled into the software. If the signatures don’t match, the update is rejected.

On top of that, operating systems themselves add another layer of defense. Windows and macOS both enforce developer certificate checks at runtime, so an attacker would also need to compromise our Apple and Microsoft signing certificates to avoid OS-level warnings.

Compared to our previous GitHub-based distribution, this is actually a step up in security. Back then, compromising a single maintainer account could have been enough to trick clients into surfacing a malicious update. Now, even if someone compromised our Nostr key, they would still face multiple cryptographic and OS-level hurdles before a malicious build could ever be accepted by users’ machines.

We are proud to announce that Wasabi Wallet v2.7.0 is our first release fully distributed through Nostr.

Instead of relying on GitHub or DNS, clients now receive update notifications directly from notes published by Wasabi’s Nostr public key. This ensures that even in the event of infrastructure outages or black swan scenarios, we can deliver emergency fixes seamlessly.

For users, the update process remains unchanged: smooth, secure, and reliable.

For the project, this marks an important step toward resilience: guaranteeing that users will always be able to securely access their funds with Wasabi, without sacrificing privacy by restoring seeds on less private wallets.

Of course, we also want to thank relay operators for making it possible to implement features like this.

Because of how settings are implemented in Wasabi, when a CLI argument is specified (what it seems you did), modifying settings from the UI could create weird behavior. Lately we made a lot of improvements to how settings work, so it would make sense to remove this restriction, however we didn't make this "feature" yet.

🚨 New release 2.7.0 is here! 🚨

v2.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

🛠️ Many Bug Fixes

👉https://github.com/WalletWasabi/WalletWasabi/releases/tag/v2.7.0

🟠 Enhanced Bitcoin Node Integration

Bitcoin node connectivity is now more seamless. RPC endpoint handling has been refined for smoother setup, with support for onion-service RPC interfaces.

Additionally, Wasabi no longer bundles bitcoind binaries, while block downloading has been simplified and made more dependable.

🎨 Refreshed UI with Icons & Animations

The interface has been given a polished update. Subtle animations and a balanced color scheme breathe new life into Wasabi’s design, making it both cleaner and less aggressive.

⚙️ Dedicated Config Files Per Network

Each network Mainnet, Testnet4, and Regtest — now has its own independent configuration file. Switching to test networks is easier and your preferences are always preserved.

🤯 Stronger & Smarter Coordinators

Coordinators are automatically published as onion services right out of the box: no manual Tor setup needed. Coordinators can now also run on pruned nodes in blocksonly mode.

Plus, fallback fee rate providers were implemented (mempool.space and blockstream.info), ensuring accurate fee estimates, even if your node can’t provide them.

🛠️ Refinements & Fixes

- Full-RBF by default: All transactions are treated as replaceable.

- Resilient HTTP communication: Smarter retry handling makes connections sturdier.

- Seed recovery fixes: Annoying typing issues are resolved.

- Sharper fee estimations: Precise decimal calculations with no rounding loss.

- NBitcoin updated to 8.0.14: Latest Bitcoin protocol improvements included.

- Clearer terminology: “Backend” is now called “Indexer.”

- Lean codebase: Legacy components like TurboSync and BlockNotifier removed.

- Safer Coinjoin handling: Excluded Coins can only be changed when Coinjoin is paused.

- Donation Button removed from Main Screen: The button is gone, but donations are still possible via the search bar.

- Conflux by default: Better Tor configuration for improved connectivity.

It currently only supports ip:port but we are adding support for .onion and dns as well, will release soon

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.

This is expected, Wasabi is not (yet?) a mobile wallet

As we do not have a mobile version, we do not display download links on mobile. This was already the case on last version. Open on Desktop you will see the links ;)

New skin for our website https://wasabiwallet.io/ 👀

This page weighs only 125 kb (156x less than previous version!), doesn't use javascript, and present most of the core values and features of a FOSS Wasabi Wallet!

No, Wasabi connects to the RPC interface of your Node, which is not made to be exposed

Every request in Wasabi is made through Tor (if enabled)

Currently, the only source for those filters is a specified Bitcoin Node.

So if you have a full node that provides filters, your Wasabi's client can connect to it and fetch them.

In the future we will enable more sources.

🚨 New release 2.6.0 - Prometheus is here!

Wasabi Wallet v2.6.0 "Prometheus" marks a significant milestone in our survival strategy, delivering major improvements in resiliency by eliminating dependency on centralized infrastructure while making it harder to stop.

💥 Support for Standard BIP 158 Block Filters

💻 Full Node Integration Rework

🔐 Create & Recover SLIP 39 Shares

💪 Nostr Update Manager

And more, check out the notes: https://github.com/WalletWasabi/WalletWasabi/releases/tag/v2.6.0

Default

🚨 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!

https://github.com/WalletWasabi/WalletWasabi/releases/tag/v2.5.0

💪 3rd Party Providers for Fee & Exchange Rate

Wasabi now fetches the Fee Rate Estimations & Exchange Rate from configurable 3rd parties.

This change is important as it's one of the last steps in our long-term mission of making Wasabi resistant to any event!

👨‍🔧 Quality of Life Features

To thank you for your incredible support, this release is packed with long-awaited improvements!

We’re grateful for your belief in Wasabi, whether shown by donating, contributing, or simply using the software.

Test it now and discover the updates!

📦 Backend and Coordinator packaged for Linux

The Debian package now includes two extra binaries: one for the backend (Wallet API) and one for the coordinator (Coinjoin API).

This makes it easier for community members to run a backend and/or a coordinator, private or publicly

---

Wasabi is slowly becoming a lightweight, easy-to-use Bitcoin wallet with amazing privacy features, not depending on any server.

There are few, if any, that compare in the ecosystem, and we are hard at work to make sure that Wasabi is undeniably the best of its kind.

🚨 New release 2.4.0 is here! 🚨

🤫 Send to Silent Payment addresses

🎁 Donation Button

🧪 Switch to TestNet 4

📝 Release Notes in the client

Full Release Notes & Download:

https://github.com/WalletWasabi/WalletWasabi/releases/tag/v2.4.0

🤫 Send to Silent Payment addresses

Silent Payments are addresses that you can privately reuse! Perfect for tips, donations, or recurring payments between the same entities.

Wasabi Wallet is among the first to support this cutting-edge feature. Receiving support is coming soon!

🎁 Donation Button

Wasabi Wallet is FOSS & relies on contributions for maintenance and improvements.

You can now support contributors directly from the app with Silent Payments, showcasing this feature’s potential.

We hope more Bitcoin projects adopt this funding strategy!

🧪 TestNet 4 Support

We’ve switched from TestNet 3 to TestNet 4!

TestNet 4 resolves many of the issues plaguing its predecessor, offering a smoother testing experience.

Don’t forget to grab new coins from a faucet!

📝 Release Notes in the client

Release Notes Highlights will now appear on the first launch after an update.

You can still access the full release notes on GitHub for all the details.

Additional Note:

We’re excited to finally release the first part of Silent Payments, but more awesome features are on the way!

We're also assessing potential privacy risks from sophisticated coordinator attacks and will publish a detailed statement soon, along with a plan of action if required.

🚨 Release 2.3.1 is out 🚨

This version is a stability release packed with bug fixes and preparatory changes for upcoming features

🪲 Bug Fixes

💫 Settings Layout

⤴️ Tor upgraded to v13.5.9

🚫 Buy Anything Button Disabled

Release notes & Download:

https://github.com/WalletWasabi/WalletWasabi/releases/tag/v2.3.1

🚨 New release 2.3.0.0 is out 🚨

🌐 Enhanced Tor integration

📊 Better BTC amount formatting

🔍 More insight on transactions

💰 [Beta] Payment in Coinjoin (RPC)

🔒 Trezor Safe 5 & ColdCard Q support

Release notes & Download: https://github.com/WalletWasabi/WalletWasabi/releases/tag/v2.3.0.0

This release continues our vision of simplifying the codebase and improving the resiliency of the software, while still shipping long-awaited quality-of-life features. By building stronger foundations today, we're paving the way for more exciting features tomorrow!

https://video.nostr.build/18c0fa455a11129be7987827b054ab3a80f8fc609f9b7b018205c897c30159b7.mp4

🌐 Enhanced Tor integration

Complete rewrite of our Tor integration using standard HttpClient. Better performance, clearer code, and improved identity management for enhanced security.

📊 Better BTC amount formatting

Improved readability for all amounts with instant BTC-to-Sats conversion. Cleaner, more consistent UI across all screens showing amounts: balances, fees, Coinjoin outputs...

🔍 More insight on transactions

Detailed input/output lists for all transactions, including Coinjoins and transaction preview. This long-requested feature offers insight into the privacy-enhancing effects of coinjoins and the level of anonymity achieved with each transaction. Additionally, it is now visually clear how privacy suggestions improves transactions.

💰 [Beta] Payment in Coinjoin (RPC)

Our Payment in Coinjoin feature enters beta! Currently available via RPC only. Test it out and share your feedback!

Learn more: https://docs.wasabiwallet.io/using-wasabi/RPC.html#payincoinjoin

🔒 Hardware Wallet Updates

Added support for Trezor Safe 5 & ColdCard Q with HWI 3.1.0 update.

Sorry for forks :D

We've redesigned our network isolation code (Tor integration)!

Originally, .NET lacked native support for routing HTTP traffic through Tor, so we built custom solutions. Over time, this became unsustainable, requiring us to manually implement many new low-level features like redirects and compression.

Now, with .NET 6’s native SOCKS proxy support, we've switched to a more efficient HttpClient. This simplifies our code, improves performance, and makes it easier to implement new features without headaches. It also improves clarity on how Tor integration works and drastically reduces the potential for errors.

Better building blocks are key to keep improving Wasabi!

Thanks for the feedback! Wasabi currently doesn't support any kind of localization. Only English, USD as fiat currency, American formatting standards. It is definitely something we're looking into, but it will take time.

For the amount formatting specifically, we use the . as a separator for decimals and a thin space for thousands separation. Even if localization would be much better, the complete lack of comma avoids possible confusion.