Wasabi Wallet v2.6.0 released w/ SLIP39 multi share support \ stacker news ~bitcoin

pull down to refresh

Wasabi Wallet v2.6.0 released w/ SLIP39 multi share support wasabiwallet.io/

8251 sats \ 100k boost \ 61 comments \ @kruw 5 May bitcoin

Wasabi is a privacy wallet for Bitcoin only, 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

Wasabi can now synchronize using BIP 158 filters without requiring a backend/indexer. You can connect directly to your own node, significantly enhancing synchronization speed and resilience. This improvement allows clients to operate fully sovereign and independent of specific servers.

💻 Full Node Integration Rework

The previous integration was replaced with a simpler, more flexible system which is not limited to a specific Bitcoin node fork and doesn't depend on the node running on the same machine as Wasabi, or require modifications to the node's configuration.

Simply enable the RPC server on your node and point Wasabi to it, ensuring all Bitcoin network interactions happen through your own node, bypassing third parties for getting blocks, fee estimations, block filters, and broadcasting transactions.

🔐 Create & Recover SLIP 39 Shares

You can now create and recover wallets with multiple share backups using SLIP 39. Simply specify the number of shares and the required threshold for recovery (e.g., a 2-of-3 scheme requires 2 of the 3 generated seed phrases to unlock the funds).

This offers additional flexibility for backups, as individual shares can be compromised without endangering funds.

Special thanks to Trezor (SatoshiLabs) for sponsoring this amazing feature.

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

This considerably improves resiliency, allowing updates even if GitHub is inaccessible. Naturally, the manager still verifies that displayed updates are signed by our secure certificate.

🤯 And more…

We've also been busy under the hood with several miscellaneous improvements:

-Updated Avalonia to v11.2.7, fixing numerous UI bugs (including restoring Minimize on macOS Sequoia!). -Added a configurable third-party fallback for broadcasting transactions if other methods fail. -Changed our Windows Code Signing Certificate, now using Azure Trusted Signing. -Fixed numerous bugs, improved our codebase, and enhanced our CI pipeline. -Provided the option to avoid using any third-party Exchange Rate and Fee Rate providers (Wasabi can work without them). -Rebuilt all JSON Serialization mechanisms avoiding default .NET converters. Serialization is now stricter.

view all related items

21 sats \ 1 reply \ @ek 5 May

RIP #971491 as top boost

21 sats \ 0 replies \ @028559d218 5 May

The top post like the room for blockspace is a free market...

26 sats \ 5 replies \ @Jon_Hodl 6 May

Is there any way that you could make all of the Wasabi CoinJoin output sizes the same size or a series of the same size?

Like only have these output sizes:

1.00000000
0.10000000
0.01000000
0.00100000
0.00010000

…and anything smaller than that just gets donated to the coordinator or miners?

My biggest problem with Wasabi is that the outputs are all different and often unique sizes.

26 sats \ 3 replies \ @kruw OP 6 May

The design you described is essentially what already occurs. There are standard denominations that each client chooses from when decomposing into outputs. Participating in rounds with high liquidity helps clients to avoid creating unique values, and minimizes the leftover dust that gets donated to coordinators/miners.

Reducing the set of possible standard denominations is a tradeoff; fewer denomination options will increase the chance of matching your outputs with other users, but will result in higher waste.

21 sats \ 2 replies \ @Jon_Hodl 6 May

Ok. Cool.

My next question is how easy is it to irreversibly delete a wallet from my computer?

I want to be able to deposit, CoinJoin a while, and then delete every single remnant of the the wallet from my computer forever.

How do I do that?

21 sats \ 1 reply \ @kruw OP 6 May

Open the "Wallet Folder" from the search bar at the top, from here you can delete the .json file for an individual wallet.

21 sats \ 0 replies \ @Jon_Hodl 6 May

🫡

0 sats \ 0 replies \ @Jon_Hodl 6 May

deleted by author

131 sats \ 4 replies \ @BlokchainB 5 May

Damn I thought this wallet was dead. I used to mix often with them but haven’t in like two years

116 sats \ 3 replies \ @kruw OP 5 May

Wasabi is more alive than ever, and is even setting new world records for coinjoin transactions:

493 input coinjoin: https://mempool.space/tx/de977aab644054dbdf09572e6e815b35331ff843253fecf8cd92e25e93f8634a 652 output coinjoin: https://mempool.space/tx/c559ee0e19aa8ce15ee1191b611daf409e90ddb6eca1d887590806e04d4ebbe3

21 sats \ 2 replies \ @BlokchainB 6 May

Who’s the coordinator?

220 sats \ 1 reply \ @kruw OP 6 May

I run a coordinator on my node, you can check https://liquisabi.com or https://wabisator.com to find other coordinators broadcasting their connection info to Nostr.

21 sats \ 0 replies \ @BlokchainB 6 May

Thanks for the info!

121 sats \ 0 replies \ @longlifelearner20 7 May

The phoenix has once raised from the ashes of time and flames of fire to bridge the trust it once claim. The best wallet is here again and it is meant to stay. Im glad :)

63 sats \ 2 replies \ @anon 8 May

What's the rule of thumb regarding consolidating Utxo s after coinjoin? Seeing limited and guesswork-sounding info out there.

If someone coinjoins a single utxo of 1 BTC they may end up with big chunks but also smaller bits of 10k, 20k sats. Does reconsolidation of a few, or all, the private utxo completely defeat the privacy gains of coinjoining?

Secondly, the option to coinjoin disappears after 100% private is reached on Wasabi. Does that mean rejoining from that point is useless?

87 sats \ 0 replies \ @kruw OP 8 May

As a general rule, each additional UTXO you consolidate will decrease your privacy by some marginal amount. It's hard to give precise guidance since the observation model is different for whales vs small users and different for coordinators with large liquidity vs small liquidity.

If you start with only a single UTXO, there's a special case that triggers called Safety Coinjoins that will perform an extra remix for all of the outputs created in the initial round.

You can go to the wallet settings button from the ". . ." menu in the top right and check the coinjoin tab. Here you can increase the "Anonymity Score Target" number if you want to reduce your privacy progress below 100% again to participate in more transactions.

21 sats \ 0 replies \ @lontivero 9 May

I strongly recommend using Wasabi as a privacy-oriented wallet and not as a mixer.

This means that you should welcome both large chunks and smaller amounts (10k, 20k sats) because this increases your capacity to make payments privately and avoid change.

Having a variety of denominations makes it much easier to find combinations of coins for payments you need to make. Even if Wasabi can't avoid creating change for your transaction, only a tiny portion of your wallet will be known by someone else, and the labeling system (in my opinion, the most powerful tool in Wasabi) will help you avoid leaking more information to others.

Having very few coins, or in the extreme case only one coin, is a privacy nightmare. This means that whatever payment you need to make will involve a large portion of your wallet, which also means you cannot avoid change, and then your future payments will be trackable. For example, a wallet with only one coin generates a peel chain that is trivial to follow.

There are situations where consolidating can make sense, such as when coins are too small and you fear they could become unspendable or too costly to spend, but in general, it is not the best approach for privacy.

The "Wasabi is a mixer" mentality consists on sending to Wasabi, participate in many coinjoins and then consolidate everything to send it to a non-privacy-focused wallet. Do not do that.

Okay okay, if you want/need to do it then there are a couple of ways to do it to mitigate a bit these problems:

Coinjoin to another wallet: Wasabi can send your coins in a coinjoin to another wallet. In this case it tries to use as much coins as possible (never more than ten) and send that amount to a different wallet in a set of outputs. It doesn't do a big consolidation but it at least doesn't generate much outputs
Pay in coinjoin: It requires a few command lines but it is a super powerful tool that allows you to send money in a coinjoin where you are the one who specify the amount of the output. Here you can see a donation to El Salvador bitcoin address in a Wasabi coinjoin: https://mempool.space/tx/8c58beccc25acc763c528515b3a23bb92eeb6dc41b519ef681f76dfcc76cc19d#vout=433

21 sats \ 1 reply \ @2053456d48 6 May

I can't find links to download it for Android devices....

0 sats \ 0 replies \ @kruw OP 6 May

Wasabi is only available on desktop Linux/Mac/Windows :(

21 sats \ 1 reply \ @nichro 7 May

Was curious how it plays with hardware wallets and saw this in FAQ:

DOES WASABI SUPPORT HARDWARE WALLETS? Wasabi does support hardware wallet usage through the standard Bitcoin-core HWI, and coinjoining straight to a hardware wallet is possible, but signing a coinjoin trasaction with a hardware wallet is not implemented.

Does this mean you cannot coinjoin with wasabi without keys being hot/loaded in it (versus cold on the connected HW)?

43 sats \ 0 replies \ @kruw OP 7 May

You are correct, coinjoin isn't offered for hardware wallets. Trezor used to be able to coinjoin directly on their own device. Trezor's code still exists, but the feature is no longer maintained.

21 sats \ 3 replies \ @zuspotirko 14 May


Message: Object reference not set to an instance of an object.

Stack Trace:    at Tmds.DBus.SourceGenerator.ComCanonicalDbusmenu.EmitLayoutUpdated(UInt32 revision, Int32 parent)
   at Avalonia.FreeDesktop.DBusMenuExporter.DBusMenuExporterImpl.DoLayoutReset()
   at Avalonia.Threading.DispatcherOperation.InvokeCore()
   at Avalonia.Threading.DispatcherOperation.Execute()
   at Avalonia.Threading.Dispatcher.ExecuteJob(DispatcherOperation job)
   at Avalonia.Threading.Dispatcher.ExecuteJobsCore(Boolean fromExplicitBackgroundProcessingCallback)
   at Avalonia.Threading.Dispatcher.Signaled()
   at Avalonia.X11.X11PlatformThreading.CheckSignaled()
   at Avalonia.X11.X11PlatformThreading.RunLoop(CancellationToken cancellationToken)
   at Avalonia.Threading.DispatcherFrame.Run(IControlledDispatcherImpl impl)
   at Avalonia.Threading.Dispatcher.PushFrame(DispatcherFrame frame)
   at Avalonia.Threading.Dispatcher.MainLoop(CancellationToken cancellationToken)
   at Avalonia.Controls.ApplicationLifetimes.ClassicDesktopStyleApplicationLifetime.StartCore(String[] args)
   at Avalonia.Controls.ApplicationLifetimes.ClassicDesktopStyleApplicationLifetime.Start(String[] args)
   at Avalonia.ClassicDesktopStyleApplicationLifetimeExtensions.StartWithClassicDesktopLifetime(AppBuilder builder, String[] args, Action`1 lifetimeBuilder)
   at WalletWasabi.Fluent.Desktop.WasabiAppExtensions.<>c__DisplayClass0_0.<RunAsGuiAsync>b__0()
   at WalletWasabi.Daemon.WasabiApplication.RunAsync(Func`1 afterStarting)
   at WalletWasabi.Fluent.Desktop.WasabiAppExtensions.RunAsGuiAsync(WasabiApplication app)
   at WalletWasabi.Fluent.Desktop.Program.Main(String[] args)

Nice start lol

0 sats \ 2 replies \ @kruw OP 15 May

Ouch. What operating system did this crash on?

21 sats \ 1 reply \ @zuspotirko 15 May

Arch Linux with the newest version from the AUR

But it worked on second try so ¯\(ツ)/¯

5 sats \ 0 replies \ @kruw OP 15 May

It doesn't look like Arch is officially supported - https://github.com/WalletWasabi/WalletWasabi/blob/master/WalletWasabi.Documentation/WasabiCompatibility.md

But I'm glad it works anyway :)

30 sats \ 1 reply \ @deep 8 May

Wasabi 2.6.0 isn't just an update it's a declaration of independence. Ditching centralized infrastructure, embracing BIP 158, and giving users full sovereignty via their own nodes is a massive win for true Bitcoiners. Add SLIP 39 for hardened backups and Nostr-powered updates to dodge censorship, and this release hits every note of resilience and privacy. This is what fighting surveillance looks like clean, sharp, and unstoppable. Props to the team for building tools the powers-that-be really don’t want us to have.

10 sats \ 0 replies \ @028559d218 10 May

The AI crap really gets tiring, doesn't it?

3 sats \ 0 replies \ @aPolitical 6 May

So why did it go into hiding?

0 sats \ 0 replies \ @Dkryptoenth 5h

Wasabi Wallet is a credible app

0 sats \ 1 reply \ @SatsMate 19 May

Great to see these moves for wasabi! Will Wasabi wallet be made available on the app store anytime this year? I would really like to use it on my apple device

0 sats \ 0 replies \ @kruw OP 14h

There's some interest in creating a mobile version of the wallet. I have no timeframe for this project though.

0 sats \ 0 replies \ @clownworld 16 May

I don’t trust wasabi. The Samourai guys posted a long explanation a while back about the flaws in wasabi and how it could be traced. I don’t remember the details now, but it was pretty convincing. There was some case where a person was prosecuted and the evidence came from tracing wasabi mixed coins.

0 sats \ 0 replies \ @Thisdaystacker 16 May

Great work and more improvements on Wasabi

0 sats \ 0 replies \ @Educational_Stacker 16 May freebie

Cool update

0 sats \ 0 replies \ @63350fa578 11 May freebie

Awesome 🧡⚡

0 sats \ 2 replies \ @Jon_Hodl 10 May

Where can I find the CoinJoin coordinator fees?

There doesn't seem to be any transparency anywhere online or in the wallet?

31 sats \ 1 reply \ @kruw OP 11 May

Coordinators can no longer charge coinjoin fees since the release of Wasabi v2.2.0. However, coordinators can still earn sats by consolidating the dust amounts created by each user. https://liquisabi.com tracks the total for each round.

0 sats \ 0 replies \ @Jon_Hodl 11 May

Thanks

0 sats \ 0 replies \ @deep 10 May

Was the 100k really worth it

0 sats \ 0 replies \ @Haamiti1 10 May freebie

A nova versão do Wasabi Wallet, chamada 2.6.0 "Prometheus", traz melhorias importantes que tornam a carteira mais privada, independente e resistente à censura. Agora é possível sincronizar diretamente com seu próprio nó Bitcoin usando filtros BIP 158, sem depender de servidores centralizados. A integração com nós foi simplificada e não exige mais que o nó esteja na mesma máquina ou configurado de forma específica.

0 sats \ 4 replies \ @028559d218 10 May

I had a question about Wasabi... I understand there is a new Node RPC function. That's in fact how you connect Wasabi to your own node, correct?

I tried entering that information (login info and TOR) and configuring my node but it says RPC "unresponsive". Am I still doing something wrong? Thank you!

21 sats \ 3 replies \ @lontivero 11 May

Once you install the bitcoin node and enable the rpc interface, lunch Wasabi and it will detect your node.

0 sats \ 2 replies \ @028559d218 11 May

Thanks. I'm running the umbrel implementation... and when I enable the RPC through Umbrel's Bitcoin Core application...

I go to 'connect wallet' and it gives me a username and web address to connect to, right? Then I've tried to connect to it at which point it still says unresponsive.

What am I missing? Thank you.

42 sats \ 1 reply \ @lontivero 12 May

Your question is not about Wasabi but about Umbrel and how to expose the Bitcoin Node RPC. I don't know how your infrastructure is configured but if you have your node's RPC enabled and the RPC port is opened in your Umbrel then you should be able to connect to it and you could test the connection using bitcoin-cli. My suggest to ask to Umbrel team/community how to expose the RPC.

Finally, Wasabi requires compact filters from your node if you want to synchronize and operate without using any external filters' providers. That means that you have to enable the creation of compact filters in your node.

0 sats \ 0 replies \ @028559d218 12 May

Thank you I'll look into it

0 sats \ 0 replies \ @villawolf 9 May

💚 So glad to see Wasabi in action! This privacy-focused desktop wallet helped me a lot to check my balance and get organized again. I had been disconnected from the space for a while, and it makes me happy to see the Wasabi team still going strong. 🔐

0 sats \ 1 reply \ @Lazy_AMA 8 May

What's up with the WASABI wallet in a nutshell?

24 sats \ 0 replies \ @lontivero 9 May

Wasabi was developed by a company which closed its doors last year. Since then, a tiny group of volunteers took the responsibility to continue with the project and has been focused on guaranteeing the survival of the wallet. This means changing an originally centralized, trusted, client-server architecture to a standalone, trustless piece of software with decentralized services run by volunteers. In other words, the goal is still to completely redesign Wasabi's architecture to eliminate central points of failure and protect Wasabi users and volunteers.

Even though every release highlights user-oriented features such as Silent Payments, SLIP39, support for newer hardware wallets, and similar improvements, the most important changes are structural. These changes allow others to run coordinators, backend servers, or both. It also allows Wasabi to synchronize and operate without a central server by connecting to your own node.

The next goal for the team is to shut down the backend and let others host tiny indexers that users can connect to.

If you are interested, I explain all this a bit better in the Bitcoin Talk forum thread I posted: https://bitcointalk.org/index.php?topic=5476197.msg65272894#msg65272894

0 sats \ 0 replies \ @EmeknightPeter 7 May freebie

Where is the link to download, I can't find it

0 sats \ 0 replies \ @coinhome 7 May freebie

buena actualización, gracias

0 sats \ 0 replies \ @TadiRetata 7 May

Wasabi Wallet v2.6.0 "Prometheus" is a major leap forward for Bitcoin privacy and self-sovereignty. The new support for BIP 158 block filters lets users sync directly with their own node, eliminating reliance on centralized infrastructure and making Wasabi more resilient and censorship-resistant than ever. The reworked full node integration is flexible and easy to set up, empowering users to route all Bitcoin network interactions through their own node for maximum privacy and independence.

The addition of SLIP 39 share creation and recovery brings advanced backup flexibility, while the Nostr Update Manager ensures users can securely receive updates even if traditional channels are blocked. Combined with UI improvements, stricter serialization, and the option to avoid third-party exchange or fee providers, this release cements Wasabi’s role as a leading privacy wallet-delivering cutting-edge features while putting user control and security first.

0 sats \ 0 replies \ @d680ecaa8e 7 May

i was using this wallet since a long period of time.

0 sats \ 0 replies \ @TadiRetata 6 May

Link direct download app from offucual page

0 sats \ 0 replies \ @Dkryptoenth 6 May

Great info

0 sats \ 0 replies \ @0fd4284897 6 May freebie

I lose my sat to this wallet thought they operate no more

0 sats \ 0 replies \ @6174f49286 7 May outlawed