Quote from: 14er on June 22, 2014, 02:38:38 PM

So, Dr. H do you think this pool is vulnerable to abuse? And if so, what do you think should be done. And if NOT, why do you think so?

All mining pools are, and have always been, vulnerable to block withholding attacks.

These attacks are rare though. There were those guys mining at BTC Guild and Eligius who had a programming error in their software, having to do with how they determined whether work was above or below pool difficulty. I also read on Reddit someone claiming to be block withholding on Ghash on purpose. Those are the only cases I've heard about so far.

The real solution would be to get protection against block withholding in the next Bitcoin hardfork. Other than that, pool operators have to watch users with suspiciously bad luck. Accusing everyone with slightly bad luck is not a solution. I don't see it as a solution to stop pooled mining either, and have everyone solo mine. For most miners solo mining is not an option.

There's no reason to believe mining chips would do block withholding. That would actually require more logic on the chips.

Quote from: Krabbit on June 22, 2014, 02:53:34 PM

Help, I keep trying to find the answer to this. Why cant someone send in a huge amount of work that they have already submitted to another pool. How does GHash.io what (Non-block find work) I have submitted to bitminter and vice versa? Whats to stop some clever coder from submitting non-block finding work simultaneously to multiple pools?

Pools only accept solutions to work they sent out, not work sent out by other pools.