Topic: Wasabi Wallet - Open Source, Noncustodial Coinjoin Software - page 17. (Read 11391 times)

Min input count was too low. Anyone has input on how to solve this and what it means? I have relatively large amount of btc, so it shouldn't be a problem. What am i missing?

He owns the ability to answer to a basic Yes or No question, but he has clearly avoided this question in particular for years, along many others, while continuing this 'where proof?' childish behavior for what ever reason.  This is clearly a question he is trying his hardest not to answer.

But that's his decision, and although he might be hiding something, he truly doesn't owe us anything if he wants his identity hidden. We merely need to accept that he's simply a "contributor" for zkSNACKS. But if anyone wants to meet him in person, you can introduce yourself and ask him his name and what his actual work is in zkSNACKS, you can do that in Prague.

If you've delved into the source code, verified everything, and seen there's no problem, then kudos to you, and you have my respect. But, I'm pretty confident that the 99.9% of the users of any product won't do this. Most will simply download the binaries and, at best, verify the signature.

If you haven't verified the source code, then you need to trust the people who have written and studied the source code. Allow me to not trust liars with my privacy software.

Can you make an argument without resorting to whataboutism for once?

If you haven't verified the source code, then you need to trust the people who have written and studied the source code. Allow me to not trust liars with my privacy software.

2.1. Privacy Policy

Please refer to our Privacy Policy to get an understanding of our confidentiality obligations. You consent to the collection and use of information as described in the Privacy Policy.

2.2 Suspension or termination of services

Mixtum reserves the right to suspend or terminate access to services at any time at its own discretion, with or without reasons, with or without notification assuming no responsibility whatsoever.

For example, services may be suspended or terminated due to the following reasons:

    an actual or suspected violation of these Terms and Conditions;
    use of the service in such a manner that is conducive to the legal liability of Mixtum or Service malfunction;
    planned or unplanned maintenance, etc.

2.3 Unacceptable use

You agree that you personally will not commit, encourage or support the committal of:

    use of any unauthorized means to access the Mixtum service or use of any automated process or service (for example, spider, crawler or periodic caching of information stored or generated by Mixtum) except for the functions described in our API, as well as distribution of instructions, software or tools with this aim in view;
    modification, change, distortion or any other interference in work of the Mixtum service;
    disturbing or interference in operation of servers or networks used by Mixtum to deliver the Services;
    disabling, overload or degradation of Mixtum performance (or any other network connected to the service);
    use of the Mixtum service or website for any other purposes other than those specifically provided by these Terms and Privacy Policy;
    any illegal or fraudulent activity, as well as use of this Service in order to legalize illegal income, financing of terrorism, participation in schemes of phishing, forgery or other such falsification or manipulation;
    unauthorized spamming, pyramid schemes or any other activity duplicating unwanted messages should they be commercially oriented or of other nature.

2.4 Service updates

At any time and at its absolute discretion Mixtum can carry out unscheduled works related to the service modification, update and enhancement. We are liable to add or remove functions and cease activities of the service and website.
2.5 License and restrictions

Mixtum provides you with a personal nontransferable nonexclusive license to use the Service as it is stipulated for you by Mixtum. This license is provided under conditions and restricted to the provisions, stipulations and constraints stated in these Terms. Therewith, such license is intended for personal, noncommercial use. You may not copy, modify, create a derivative work of, decompile or otherwise attempt to extract the source code of the service or any part thereof, exclusive of data permitted by law, or expressly allowed by the Mixtum platform (use of templates, API, etc.). You may not reassign (or grant a sublicense of) your rights to use the service, or otherwise transfer any part of your rights in accordance with these Terms. These Rules do not provide you with any license or permission to copy, distribute, change or otherwise use any applications programming interface despite any provisions to the contrary. No property rights or ownership rights related to the Service are not granted to you according to these Terms. Mixtum reserves all rights that have not been expressly granted.

I'm not defending Kruw, but that, ser is such an irresponsible statement.

You probably can't trust a single of code from Kruw's contributions/work in closed source project/proprietary software - IF he did any of that. But in Wasabi I believe all code/contributions from all developers are Open Source, no?

TwistyPhrasy will never answer a question that will make Wasabi look bad, and there really isn't any way to explain why would zkSNACKs buy information from chain analysis company, if they think it's inaccurate.

(Laughable) Answers to these questions have been given in here: https://bitcointalksearch.org/topic/m.60518076. To me, the TLDR is that you can't trust a single line of code coming from these people.

He owns the ability to answer to a basic Yes or No question

He owns the ability to answer to a basic Yes or No question, but he has clearly avoided this question in particular for years, along many others, while continuing this 'where proof?' childish behavior for what ever reason.  This is clearly a question he is trying his hardest not to answer.

Those are my sentiments exactly. All I wanted was for him to state it by his own admission.

If looking to it from a viewpoint of an actual Open Source project, a contributor means that - simply a programmer who makes pull requests, and contributes code to the project/proposes changes. Your question should be if he's an official employee of zkSNACKS/who receives a salary or a sort of compensation directly from the company. Because if not, then a contributor is a contributor who works for free.

For some reason Kruw continues to claim zkSNACKs had shutdown last month but in reality it operates and continues to update Wasabi Wallet.

Kruw has labelled himself as a "Contributor to Wasabi Wallet" without explaining what that means. With him failing to even answer the question or address the point and not bother explaining what it means no matter how many times you ask, shows he is very keen to not comment on it. If that is the case, he clearly has something to hide.

How difficult can it be for him to explain what his relationship with zkSNACKs is and to explain what he means when he claims to be a "Contributor to Wasabi Wallet".

zkSNACKs did not, was not and is not shut down yet when you describe yourself as a "Contributor to Wasabi Wallet" but you are not willing to explain what that means. You already embarrassed yourself with your gutter-level conduct over recent months and now you are embarrassing yourself even further by avoiding to answer.

Yes there was:

I'm not debating for Bitcoin as more private simply because it has more users. I was merely thinking about the comparison from a theoretical perspective. The same question - If there are 10,000 CoinJoin users and then there are 100 Monero users, in theory would the users of Monero be easier to trace/identify and/or make less private?

Those are rookie numbers. The Monero users are, by far, greater in number than Coinjoin users.

And no, the anonymity set of Bitcoin is not greater than Monero, just because it might have more users. The overwhelming majority keeps them on exchanges, under KYC, and from the rest, the majority of the coins are simply kept on a self-custodial wallet, without any privacy enhancements apart from coin control. A brief look at Bitcoin's current privacy options makes this clear.