21–23 of 23 posts
I couldn't find anything with a quick search, but would be interested to read more about (client-side)? security vulnerabilities of pooled mining.
I don't know much about Bitcoins, but is there a large risk of tainted workers in a pool that are reverse engineered and have knowledge of the part of the algorithm they're helping with? Then, if they detect they mined a coin, they disconnect from the pool, don't report the result, and take all the profit. I couldn't find anything with a quick search, but would be interested to read more about (client-side)? security…
There is a theoretical attack where the miner throws away a successful block, so nobody gets the reward and the pool suffers. But it's a whole lot of work just to annoy people and this solution-witholding attack isn't viewed as a real problem: http://bitcoin.stackexchange.com/questions/1338/how-is-block...
I have written a proxy pool server ( https://github.com/dogestreet/proxypool ) in Haskell if anybody wants to check it out. It's a Stratum to Stratum protocol proxy, it lets you create a mining pool that mines into another mining pool. (Disclaimer, only P2Pool upstreams work for now, I'm trying to get it to work with stratum-mining).