And we also have a "catastrophic" problem with PoW:
No, it you read what I wrote it was a
hypothetical, modified version of AES which does not diffuse to all of the output bits, which is specifically not what real AES is designed to do. No one has identified an actual problem.
Ok, let's make it more practical then. Citing the experts below:
As I said above, no one has identified an actual problem. His concerns are theoretical and other experts disagree. No one has identified an actual problem.
EDIT: I'd add that the DoS issue is a potential problem, but is somewhat mitigated by the optimizing of the algorithm and the code that occurred. Initially (when that comment was written), it took hundreds of milliseconds to verify a hash which is indeed a lot of time and a big DoS vulnerability. These days with the optimized hash code and multithreaded verification, the effective time is well under 10 ms, which is close enough to network latency to serve as an effective throttle on DoS.
Actually, my bad, this was a point that should be posted in XMR #badcrypto thread. Anyway. The reason we are here:
Wow, I just saw that. I agree with tacotime, it looks intentional.
So you mean the BCN engine was curbed all this time, and they just add to remove it to artificially increase it?
That's disgusting.Blame BCN developers - instamine yourself. Nice catchphrase you got here
And here i thought people went to MRO to have a clean start but nope! instamining it with a fast linux hash... Cool!

You're welcome to optimize your own miner if you're so interested; you have the source code. Artforz GPU mined Bitcoin for a long time on his private OCL code on 4870s and got thousands of them. Bitcoin survives to this day, or so I'm told.
You're the developers after all.
It's a good approach for a developer: we're instamining - you can too, if you're good enough! Promising coin - no shit. 
"Fair launch"

"Disgusting"

"You can instamine too"

Monero #REKT
