Quote from: mdude77 on April 08, 2014, 01:10:08 AM

Quote from: wizkid057 on April 08, 2014, 12:52:20 AM

The pool does this by using unique extranonce/coinbase data for every connection. It also checks for duplicate submissions.

I'm only using one connection, that's why I'm using the proxy. How would I know if I was getting duplicate submissions? I don't recall seeing rejects/dupes/stales anywhere in the stats. Presumably the proxy would tell me if something was rejected. And presumably I'd notice if my payout wasn't in line with my hashrate. Assuming that dupes/rejects are properly not included in my shares.

What about the S1 itself, or any other large mining equipment? Has anyone reputable audited the output of the S1 to make sure all is copacetic? 200gh/s (OCd) is a lot of hashes to verify everything is working right. Has anyone fed it controlled data and verified the output is sufficiently random to indicate it's working properly? I think I know enough about mining works to think that a hash is a hash is a hash, so if it appears to be generating good hashes, presumably at sometime it would generate a hash that equates to a block?

Just thinking out loud here.

M

The hash verifies the block, and the block verifies the hash. (Otherwise the hash is just a bunch of random letters and numbers, unrelated to anything.) The block includes the nonce that is generated by your miner. Each share that you submit to the pool must include both the hash and the un-hashed nonce*. Otherwise you could be submitting nonsense to the pool and getting credit for it. It's easy for the pool to verify that the shares that you submit are valid hashes of valid blocks.

*and other info maybe? Or does the pool just need the nonce, and all the rest of the block is pre-determined? I suppose it depends on the mining connection protocol: Stratum is pre-determined while GetBlockTemplate needs more?