He is making 100% offtopic accusations that are based on exactly nothing to back them up, nothing even slightly relevant.
He is also one of the most qualified people on this forum to review anonymity solutions, having written his own white paper on the subject, so even a cursory glance is valuable.
evidence:
https://bitcointalksearch.org/topic/m.13211623Let's hear why this solution is different to Dash's and then we'll take it from there.
Clarification. I didn't release the white paper. But since it is no longer of proprietary value to hide it since I am no longer going to implement
Zero Knowledge Transactions, then I will endeavor to clean up the white paper and release it sometime this year. Hopefully I can find time within the next couple of months.
ZKT combines Cryptonote with Mixles' Compact Confidential Transactions. Shen-noether accomplished a similar design but combining with Blockstream's Confidential Transactions.
So these are End-to-End Principled anonymity that hide both sender and value. No simultaneity crap like Dash and this new crap from the infamous plagiarist John Conner.
The reason I am not implementing it because it requires obscuring your IP address and all other metadata, which is impractical. Apparently Monero is implementing it (at least they are toying with implementing it) and so no need for me to duplicate their effort.
Only Zerocash can give us reliable anonymity that is immune to metadata. So for now I put anonymity on the back burner and we will come back to Zerocash if we first solve the
SUSTAINABLE, DECENTRALIZED, PERMISSIONLESS block chain issue, since that is more important. No design yet can truly claim those properties.
As for resource issues, reliable anonymity will not be cheap. Thus it probably can't be for every transaction. It will probably need to be an optional set of coins. In Zerocash they name the anonymous set of coins 'zerocoins' (not to be confused with Zerocoin).
My main grip with John Conner is he doesn't put all the technical details in a white paper, because he is apparently wants to avoid peer review. Smooth doesn't have time to reverse engineer his half-assed white papers either. So we can't entirely explain the flaws without wasting a lot of our valuable time. But I can already tell you this chainblender is flawed at least in that it has a simultaneity requirement which thus violates the End-to-End Principle. Looks like there are other flaws similar to the masternode concept of mixing (which Evan of Dash has apparently finally admitted).