Topic: Wasabi Wallet 1.0 Is Released (Read 4126 times)

Thanks for showing the info. Now the only question is how good is the UI/UX? People who use desktop have better tolerance against bad UI/UX, but it's different for those who mainly use smartphone.

They definitely should have option to choose between Wasabi's coordinator or their own coordinator though.

P.S. this is my last reply, before we're going off-topic too much.

Wasabi Wallet still supports coinjoining with free coordinators. You can see a live feed of coinjoin transactions and the coordinators that staged them at https://liquisabi.com

zkSNACKs discontinued their coinjoin coordination service though.

zkSNACKs was the default coordinator of the Wasabi wallet. As you realized, you can no longer do coinjoins through zkSNACKs. There are other coordinators though if you want to stick with Wasabi. If you check this sub-board, you will find a more recent Wasabi thread, started and maintained by a disgusting and untrustworthy human being called Kruw. I wouldn't recommend you to touch anything connected to him and his honeypots and check his trust rating while you are at it.

Another coordinator you can try is opencoordinator or the fork of Wasabi called Ginger Wallet.
There is also JoinMarket, a different coinjoin implementation altogether.

I just started reading about Wasabi, as I wanted to use a non-custodial wallet with integrated TOR and found out Wasabi coinjoin making the BTC transactions almost anonymous, but unfortunately it came to my knowledge that coinjoin support has been withdrawn from the Wasabi wallet as declared by zkSNACKs.  Here is reference https://blog.wasabiwallet.io/zksnacks-is-discontinuing-its-coinjoin-coordination-service-1st-of-june/

 
It still has Tor though, which is what my initial aim was.  So, I am still happy.  Aren't you?

Please update Wasabi wallet to latest version v1.1.12.8 if you want to  avoid compatibility issue especially connected with Trezor Model T hardware wallet that has latest firmware v2.3.5.
Wasabi devs fixed this and few other bugs and minor issues with recovery words and tor, and you can read more about it in github release notes:
https://github.com/zkSNACKs/WalletWasabi/releases

Great thanks, I'll refer them to that if needed.


Yes I know about their free service but it requires a minimum fee which my transaction doesn't have. So I guess I'll have to use their paid service if I don't succeed in getting the receiver to perform a CPFP. Thanks.


Provided it's not rebroadcasted...


Yes that's why I didn't use those "free" accelerators. The only transactions I intentionally broadcasted were my double spending attempts. However I haven't kept my wallet shut down for 2 weeks so either it might be rebroadcasting in the background or some other service which I have no control over is doing it...

yes.
I actually wrote a tutorial a while back on how to execute an cpfp as a sender using electrum. For a receiver, it's actually more or less the same... If you point them towards this thread: https://bitcointalksearch.org/topic/--5285192 they can ask for help in case they don't succeed (depends on which wallet they're using tough... It might require them to export private key(s) from their current wallet and import them into electrum if they want to follow the walktrough... In which case they need to be extra carefull not to compromise their keys)

I've seen good things from viabtc... They have a free and a payed accelerator service, and they're legit... They own a pretty big pool, so they're able to deliver what they promise

Pruning happens if the limit of the mempool is over the limit set by the node operator OR if the unconfirmed transaction is older than x hours (default 2 weeks). So it should be pruned from most mempools in 2 weeks no matter what the feerate was




To be honest, i have no idear if wasabi automatically rebroadcasts transactions... Maybe you can restore your wasabi wallet from seed by creating a new wallet but re-using the same seed... Not reopening the original wallet untill the transaction has been dropped.
It's also possible you keep rebroadcasting the transaction by your efforts to fix the issue tough... For example: sometimes people start using those "free" rebroadcasting websites because they think it'll fix their problem, but all those sites do is fetch the raw transaction and rebroadcast it, making it harder to double spend or to require more time to wait untill the transaction dissapears from most mempools.

I could ask for that, so this means they would need to spend the output from the unconfirmed transaction with a higher fee and send it to one of their addresses, right?


Yes I've seen some of those but they charge way too much. Do you have some that you could recommend?


It was lower than that. At some point I hoped for it to get purged but it didn't, so it's not low enough for it to get purged but not high enough to get confirmed...

---

Indeed, I found this https://github.com/bitcoin/bitcoin/pull/9312, so it appears 3 days was the old value and now it's 2 weeks.


I'm not intentionally rebroadcasting but it seems to be happening, https://live.blockcypher.com displays a received field for transactions and for my transaction it's regularly updated. Do you know how I can know the whereabouts of the rebroadcasts, what triggers them and how many times and when my transaction was rebroadcasted?

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.

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

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

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?).

@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?

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???

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.

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.

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.

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

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.

Found some additional information about this wallet on their GutHub:



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.