> This is incorrect.
I didn't say that was correct, I was just saying that's what the article (incorrectly, in my opinion) appears to say. I'm not sure who's misunderstanding who...
> If sha256 is broken so badly that arbitrary outputs can be chosen
It's not about sha256 being broken or not, but about the way it is being used for mining (being used incorrectly != broken hashing algo). Even though I agree, if it was being used improperly we would have noticed by now - I could have chosen a better example.