Wasabi Wallet 1.0 Is Released

[witcher_sense]

Recently, Wasabi Wallet has released an official response to Twitter hack https://blog.wasabiwallet.io/wasabi-response-twitter-hack-bitcoin/ but shortly after that they deleted it from blog page. Archive version can be found here https://archive.is/tBm7g

Who knows the reason why they suddenly changed their minds and chose not to response whatsoever?

I mostly agree with what written in the aforementioned article. We can't blame open software for being open. We can't blame decentralized bitcoin protocol for being decentralized, neutral and permissionless. We can't blame people defending own rights, privacy, no one should ban people from using open software and open protocols. Most people using privacy-focused software such as Wasabi are not criminals, they just claim their rights on privacy and freedom of speech.

[cryptomaniac_xxx]

[]

I guess they felt that there's no need to explain it further, they developed it to be use for privacy focused, not to be taken advantage of criminals, in this case the supposedly twitter hacker.

[nopara73]

--snip--

Maybe because their statement could be twisted, then used to attack them? Besides, silence is golden.

This. In a nutshell.

But I can elaborate though: There was some miscommunication internally. Journalists were asking for comments, but releasing articles before we get to respond, so I told the guys that next time try to respond in a more timely manner.
Then someone who's still new thought my intention with that comment was to try to get more media attention out of it as soon as possible, so he wrote and published the article, and by the time I woke up... well, you know the rest.

[Baofeng]

Very weird that a competitor would take this into public, A Statement on two discovered vulnerabilities in Wasabi Wallet.

[bob123]

Very weird that a competitor would take this into public, A Statement on two discovered vulnerabilities in Wasabi Wallet.

This is currently being discussed in a separate topic.

[Wind_FURY]

Plebs may now mix their coins through CoinJoin/Wasabi wallet/Chaincase coordinator, https://pastebin.com/evgcRh9v



Chaincase is also developing an IOS CoinJoin app, I believe with Tor built in, https://chaincase.app/

Bitcoin privacy, and anonymity in your pocket.

[Wind_FURY]

Plebs may now mix their coins through CoinJoin/Wasabi wallet/Chaincase coordinator, https://pastebin.com/evgcRh9v



Chaincase is also developing an IOS CoinJoin app, I believe with Tor built in, https://chaincase.app/

Bitcoin privacy, and anonymity in your pocket.

Aside from my skepticism since it's first time i heard about Chaincase, maximum 6 participant is worrying from privacy perspective.
The privacy could broke easily if majority participant is being stupid (e.g. combine multiple input from different source on a transaction).

Wait for its development, I believe it's currently in beta. Their coordinator is currently online, but their IOS app is to be available maybe in a few more months.

[bob123]

Aside from my skepticism since it's first time i heard about Chaincase, maximum 6 participant is worrying from privacy perspective.
The privacy could broke easily if majority participant is being stupid (e.g. combine multiple input from different source on a transaction).

Indeed. An anonymity set of 6 is ridiculously bad.
Even if no one is trying to break the privacy, it already is bad. And additionally the attacks are quite easy (e.g. majority inputs from the same user).

I'd definitely not recommend to rely on an anonymity set of 6.

[witcher_sense]

Their website doesn't help though, since it doesn't give any info (social media, source code, etc.)

Found some additional information about this wallet on their GutHub:

A non-custodial iOS bitcoin wallet supporting Chaumian CoinJoin.

The main privacy features on the network level:

    Tor-only by default.
    BIP 158 block filters for private light client.

and on the blockchain level:

    Intuitive ZeroLink CoinJoin integration.
    Superb coin selection and labeling.
    Dust attack protections.

special thanks to Wasabi for making this possible

Chaincase is a Xamarin.Forms application built on top of the famed Wasabi Wallet privacy wallet.

It binds to Tor.framework for an anonymous connection to the outside world

This is experimental beta software. Your feedback is greatly appreciated

Source: https://github.com/chaincase-app/chaincase

So, it is essentially a Wasabi fork created for iOS users and allows for CoinJoin mixing between Wasabi users and Chaincase users if they both choose the same coordinator. I was wondering if it is possible for iOS app users to use zkSNACKs as default coordinator. It would be interesting to have an opportunity to mix coins with high anon sets on your iPhone. Crossplatform solutions for transaction obfuscation is what that is going to make bitcoin more fungible. If people of different operating systems and platforms unite and start doing mixing for every  transaction, it will make surveillance companies obsolete.

[Chikito]

My ledger device can't be connected to the Wasabi wallet, I had many times disconnect and connecting USB cable and I was set up my device also, but still, the wallet won't detect my device.

some information:

- ledger nano s
- firmware version 1.5.5
- wasabi wallet version 1.1.12.2

is there I missing something? my ledger just worked fine using electrum and ledger live.

[ABCbits]

My ledger device can't be connected to the Wasabi wallet, I had many times disconnect and connecting USB cable and I was set up my device also, but still, the wallet won't detect my device.

some information:

- ledger nano s
- firmware version 1.5.5
- wasabi wallet version 1.1.12.2

is there I missing something? my ledger just worked fine using electrum and ledger live.

According to patch note (https://github.com/zkSNACKs/WalletWasabi/tree/v1.1.12.3), the problem is fixed on Wasabi 1.1.12.3

But if you still face error, you could open Logs.txt to diagnose the problem, it's located on

Code:

~/.walletwasabi/client

[Real-Duke]

It should do again after update to the latest 1.1.12.3
I have just connected my Ledger Nano S and everything works flawless.

[Chikito]

Thanks all, my ledger has detected after updated to 1.1.12.3

I just surprise got a different address, when I checked evidently wasabi use path m/84'/0'/0' by default, while electrum I use before m/84'/1'/0'. I also can't find how to change the path in wasabi.

[Pmalek]

some information:

- ledger nano s
- firmware version 1.5.5

You are using an outdated firmware version for your Ledger Nano S. Since 1.5.5, firmware versions 1.6.0 and 1.6.1 came out. You should probably update your Ledger. Take a look at al the changes that were made in the last two firmware releases:
https://support.ledger.com/hc/en-us/articles/360010446000-Ledger-Nano-S-firmware-release-notes

- App capacity has improved.
- A new user interface was created that makes it easier to navigate the device.
- A bug that reset the device randomly has been fixed.

[Aaron2020]

almost 24 hours and my confirmation is still not confirmed. i set 400 miner fee....

the problem is i sent this to a mixer and after 24 hours they will delete all data and all my payments will be ignored! so i cant afford to have wasabi take 3 days to send it!!

please advise why my payments are taking forever to confirm

i did 400 MINER FEE. custom fee . and it takes this long for confirmation???

[Pmalek]

@Aaron2020
You broadcasted a transaction with a 400 sat/vByte transaction fee and it's still unconfirmed? I find that hard to believe because the current state of the mempool shows that transactions with 100-120 sat/vByte are likely to confirm in the next block. Let alone 400 sats. And I doubt it was any worse yesterday.

Has the transaction confirmed in the meantime and if not, care to share the transaction hash?

[bob123]

i did 400 MINER FEE. custom fee . and it takes this long for confirmation???

First, you should actually describe what exactly you did.

You did not choose a "400 miner fee".

So.. open your wallet and tell us what exactly you have chosen as your fee. Tell us whether it got broadcasted (is/was the backend connected?).

[kaicrypzen]

Hi

I have a transaction that has been stuck for a couple of weeks because of a low fee. The transaction doesn't have change so I can't use CPFP and since it was built using Wasabi it's not tagged as an RBF so I can't replace the fee and broadcast it using another wallet or service. I've read somewhere that a transaction that stays in a mempool for 3 days gets ejected but it looks like my transaction is broadcasted regularly. I've removed Transactions.dat from Wasabi's Data Folder to have the coins appear back in my wallet and tried double spending them with a higher fee, to myself and to the original address. I tried it with Wasabi, Electrum and broadcasting through blockchain.com, nothing works and I get either an error of double spending or conflict, which was somehow expected.

Any idea on how I can unstuck it?

Thanks

[DaveF]

Can the person receiving it create a CPFP transaction or is it to an exchange / business?
Wasabi does not flag RBF so you can't do that.
There are paid transaction accelerators out there and some free ones that might help.

How low a fee did you use? The fees have dropped below 10/sat b a few times over the last few weeks.

-Dave

[mocacinno]

Hi

I have a transaction that has been stuck for a couple of weeks because of a low fee. The transaction doesn't have change so I can't use CPFP and since it was built using Wasabi it's not tagged as an RBF so I can't replace the fee and broadcast it using another wallet or service. I've read somewhere that a transaction that stays in a mempool for 3 days gets ejected but it looks like my transaction is broadcasted regularly. I've removed Transactions.dat from Wasabi's Data Folder to have the coins appear back in my wallet and tried double spending them with a higher fee, to myself and to the original address. I tried it with Wasabi, Electrum and broadcasting through blockchain.com, nothing works and I get either an error of double spending or conflict, which was somehow expected.

Any idea on how I can unstuck it?

Thanks

The default setting on the reference client is 2 weeks not 3 days (at least, it's 2 weeks in the version i'm running, which is not 0.21.0, but still i'm running a relatively recent version)...
So, if you stop rebroadcasting, most (but not all) nodes should have dropped your transaction after 2 weeks...

Other than that, DaveF already gave your other options: pay a big mining pool (don't entertain offers from newbies that promise to "mine" your transaction) or talk the receiver trough a CPFP.