Damus
Wasabi Wallet profile picture
Wasabi Wallet
@WasabiWallet

Open-source, non-custodial, privacy focused Bitcoin wallet for Desktop

Relays (17)
  • wss://nos.lol – read & write
  • wss://relay.nostr.band – read & write
  • wss://soloco.nl – read & write
  • wss://relay.damus.io – read & write
  • wss://nostr.fmt.wiz.biz – read & write
  • wss://nostr.oxtr.dev – read & write
  • wss://relay.primal.net – read & write
  • wss://eden.nostr.land/ – read & write
  • wss://nostr.land/ – read & write
  • wss://nostr.oxtr.dev/ – read & write
  • wss://nostr.thesamecat.io/ – read & write
  • wss://nostr.wine/ – read & write
  • wss://offchain.pub/ – read & write
  • wss://relay.bitcoinpark.com – read & write
  • wss://relay.mostr.pub/ – read & write
  • wss://relay.nostr.bg/ – read & write
  • wss://relay.snort.social/ – read & write

Recent Notes

WasabiWallet profile picture
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.
WasabiWallet profile picture
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.
WasabiWallet profile picture
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.
WasabiWallet profile picture
🚨 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.
WasabiWallet profile picture
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.
WasabiWallet profile picture
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 ;)
WasabiWallet profile picture
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.
WasabiWallet profile picture
🚨 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