Wasabi Wallet - Total Privacy For Bitcoin

[Kruw]

Problem is that if Wasabi backend is not working there is no way to run Wasabi wallet even with your own node,

You're wrong, I'm running my own Wasabi backend on my own node. Anyone else can connect to it to synchronize too:  https://coinjoin.kruw.io/

This means that if wasabiwallet.io is ever taken down, everybody's client software will need to update, with another backend.

You're wrong, there's no client update necessary, you simply just edit the 'Backend URI' text field in your client's global settings.

[JollyGood]

As Ginger Wallet is effectively a clone built on the Wasabi Wallet source code, the same issue would probably apply to them unless they modified something within the code when they released their wallet. In the event the wallet is no longer accessing the designated URL, if it will be as simple as replacing it with another they should have announced provisions for that possibility (with a set of instructions) with every new release.

I just checked the source code, yet again. Indeed, there is a BackendUri variable pointing to "https://api.wasabiwallet.io/" by default: https://github.com/WalletWasabi/WalletWasabi/blob/e8a6e55737b554276948a403aab2fb070b3fe671/WalletWasabi/Helpers/Constants.cs#L12.

This means that if wasabiwallet.io is ever taken down, everybody's client software will need to update, with another backend. And until that new API server is created, distributed and updated in a new version of the client, Wasabi users cannot access their wallets. Why is this designed so centralized and permission-requiring?

[Pmalek]

Here is what I find extremely suspicious about your account activity: this is your first and only post in the forum yet you created the account on 22nd June 2024. The timing of your post is highly suspect even though it fits in with the problems that were being faced by Wasabi Wallet at the time. Instead of contacting Wasabi Wallet to answer your query, you decided to post in this thread and that is what has been noticed.

It could be just a coincidence but also a cheap attempt to add more importance to the topic and generate fake conversations. One could rightly ask how is it that an account that was never active before and never posted anything suddenly decided to post during a short time while the service was offline? And it was for a question that Kruw can answer simply plus advertise his own backend uri.

[JollyGood]

In this particular matter, I think it is easy to conclude the post from the dubious account was definitely an opportunity for Kruw to reply  stating the name of his co-ordinator and that alone does look very convenient as well as highly suspicious. No doubt there is a possibility no matter how tiny that it was a coincidence (after all he did mention two other services at the same time that he is not connected to) but many here will probably not buy in to that.

It could be just a coincidence but also a cheap attempt to add more importance to the topic and generate fake conversations. One could rightly ask how is it that an account that was never active before and never posted anything suddenly decided to post during a short time while the service was offline? And it was for a question that Kruw can answer simply plus advertise his own backend uri.

[BlackHatCoiner]

You're wrong, there's no client update necessary, you simply just edit the 'Backend URI' text field in your client's global settings.

Still. Users have to update their Backend URI. Why is this designed so centralized? What's the point of the API server?

As Ginger Wallet is effectively a clone built on the Wasabi Wallet source code, the same issue would probably apply to them unless they modified something within the code when they released their wallet. In the event the wallet is no longer accessing the designated URL, if it will be as simple as replacing it with another they should have announced provisions for that possibility (with a set of instructions) with every new release.

Ginger wallet comes with its own API server: https://api.gingerwallet.io/. It includes it in the link you provided.

It could be just a coincidence but also a cheap attempt to add more importance to the topic and generate fake conversations. One could rightly ask how is it that an account that was never active before and never posted anything suddenly decided to post during a short time while the service was offline? And it was for a question that Kruw can answer simply plus advertise his own backend uri.

Eh... I think you're giving him too much attention. And I think it's pointless to expect him to answer you honestly, without sticking to your immoral "Mixer Advertising" background.

[dkbit98]

You're wrong, I'm running my own Wasabi backend on my own node. Anyone else can connect to it to synchronize too:  https://coinjoin.kruw.io/

So you are telling me that you were the only guy in the whole world who was able to run Wasabi wallet when their official backend was not working because of ''financial issues'' for around 12 hours?  
Something is seriously wrong with everything you say, and I have a feeling you are slowly turning wasabi into one small cult with your small backend.
Your financial situation must be much better than from wasabi devs...

[Kruw]

So you are telling me that you were the only guy in the whole world who was able to run Wasabi wallet when their official backend was not working

Obviously not, did you stop to consider that the code I'm running is completely open source? Everyone in the whole world who has their own client also has their own backend, both are downloaded simultaneously: https://github.com/WalletWasabi/WalletWasabi

[dkbit98]

Obviously not, did you stop to consider that the code I'm running is completely open source? Everyone in the whole world who has their own client also has their own backend, both are downloaded simultaneously: https://github.com/WalletWasabi/WalletWasabi

Didn't you or one of ex-Wasabi team members nopara73 said that you don't know who to write code when everyone asked about many wasabi commits on your github page?
Than I see no reason why me or anyone else would use code for that backend, and I never saw anyone claiming to use your version of backend.

- kruw can not code

Someone is liyng here again, you, nopara73 or both of you.

- kruw has no website

This is also a lie, btw.
Or ignorance.

[Kruw]

Didn't you or one of ex-Wasabi team members nopara73 said that you don't know who to write code when everyone asked about many wasabi commits on your github page?

I don't know how to write code, my only pull request to Wasabi simply adds a single line of text to warn users not to forget their passwords: https://github.com/WalletWasabi/WalletWasabi/pull/12207

Someone is liyng here again, you, nopara73 or both of you.

So it turns out the liar was dkbit98 

[NotATether]

As Ginger Wallet is effectively a clone built on the Wasabi Wallet source code, the same issue would probably apply to them unless they modified something within the code when they released their wallet. In the event the wallet is no longer accessing the designated URL, if it will be as simple as replacing it with another they should have announced provisions for that possibility (with a set of instructions) with every new release.

I just checked the source code, yet again. Indeed, there is a BackendUri variable pointing to "https://api.wasabiwallet.io/" by default: https://github.com/WalletWasabi/WalletWasabi/blob/e8a6e55737b554276948a403aab2fb070b3fe671/WalletWasabi/Helpers/Constants.cs#L12.

This means that if wasabiwallet.io is ever taken down, everybody's client software will need to update, with another backend. And until that new API server is created, distributed and updated in a new version of the client, Wasabi users cannot access their wallets. Why is this designed so centralized and permission-requiring?

I think the reason for these designs being so brittle compared to let's say the Bitcoin protocol itself is because the development team assumes their program is going to be the only one functioning with this sort of API, such that in case the service does go down (like Samourai), it spells death to the API they're using as well (bye bye Whirlpool).

If people see that there are other teams with forks of their software and they still use a similar sort of API, they should at least try to reach out to the other teams to attempt to coordinate a common standard for the backend/API or whatever is behind the scenes so that users can easily switch from one to another. But that's hard to do unless you gather all these people at a Bitcoin conference.

[JollyGood]

Even with the their latest release of Wasabi Wallet, the changing of a coordinator is as easy as clicking the settings icon and pasting the URL therefore control over the coinjoin function stays with the customer. That was also the case in the previous version of Ginger Wallet via editing the config file but what seems to be the case in their latest release the config file reverts to default without saving the settings on restart.

What that means is if you use Ginger Wallet you have to use their coordinator and pay their fees when there are free alternatives out there. On the surface, what it also means is that if the service does go down it really could be a case of bye bye for those using Ginger Wallet if their settings are not allowed to be altered. The current way around it seems to using an earlier version or using Wasabi Wallet (not running both clients at the same time).

You are right and not only specific to these wallets but in the general sense at least with any software, if a form of universal API was agreed upon by various developers (that forked a single source code for their own releases) it might alleviate any problems switching if any one URL was unreachable because a domain expired or a business decided to shut down as it was not profitable.

I think the reason for these designs being so brittle compared to let's say the Bitcoin protocol itself is because the development team assumes their program is going to be the only one functioning with this sort of API, such that in case the service does go down (like Samourai), it spells death to the API they're using as well (bye bye Whirlpool).

If people see that there are other teams with forks of their software and they still use a similar sort of API, they should at least try to reach out to the other teams to attempt to coordinate a common standard for the backend/API or whatever is behind the scenes so that users can easily switch from one to another. But that's hard to do unless you gather all these people at a Bitcoin conference.

[dkbit98]

I don't know how to write code, my only pull request to Wasabi simply adds a single line of text to warn users not to forget their passwords

I honestly don't believe anything you say at this point after you turned everything into circus show when you celebrated death of another forum member, and after you claimed to magically turn bitcoin anonymous.
At this point I wouldn't be surprised about anything related with you.

So nopara73 is not a liar when he claims that you don't have website kruw.io right?  

Let's not forget that nopara73 is the same guy who claimed Samourai wallet is a scam, but their developer is now in prison.
Nobody from wasabi wallet team is in prison, but that must be just a ''coincidence''...

[Kruw]

I honestly don't believe anything you say

I've never asked you to believe me, I told you to verify my claim, all the code is open source: https://github.com/WalletWasabi/WalletWasabi/pull/12207

[dkbit98]

I've never asked you to believe me, I told you to verify my claim, all the code is open source: https://github.com/WalletWasabi/WalletWasabi/pull/12207

I have to give you the credits for having the guts to show up your face in the latest Bitcoin Takeover long podcast.
I don't agree with many of the things you said and did in the past, but you are probably more brave than I expected, especially after losing two jobs during c0vid plandemic.
I hope you won't end up in prison soon, but your odds are not looking good.

[Kruw]

I have to give you the credits for having the guts to show up your face in the latest Bitcoin Takeover long podcast.
I don't agree with many of the things you said and did in the past, but you are probably more brave than I expected, especially after losing two jobs during c0vid plandemic.
I hope you won't end up in prison soon, but your odds are not looking good.

Thanks, at least I'll have a lot of time to lift weights and read books in prison instead of shitposting.

[dkbit98]

Thanks, at least I'll have a lot of time to lift weights and read books in prison instead of shitposting.

It would be interesting if they put you in the same prison cell with Keonne Rodriguez 

[Kruw]

It would be interesting if they put you in the same prison cell with Keonne Rodriguez 

I think it would be funny if CZ Binance and SBF FTX shared a cell.

Anyways, back on topic.

[Kruw]

Wasabi has a new Nostr pubkey: npub1jw7scmeuewhywwytqxkxec9jcqf3znw2fsyddcn3948lw9q950ps9y35fg

[Wind_FURY]

 👀



https://www.youtube.com/watch?v=v952Fd1vmOs

Kruw is the latest guest in Vlad Costea's Bitcoin podcast "The Bitcoin Takeover". I will watch it tonight for my evening amusement. I hope they mention/talk about the "disputes" that have been happening in the topic.

Vlad probably should have included some of you and it would absolutely become more entertaining.

[Kruw]

I hope they mention/talk about the "disputes" that have been happening in the topic.

Spoiler: We didn't.