The quality of posts has dropped to such a low level that all users who are participating in a paid signature campaign are added to my ignore list. If you'd like a copy of the list to improve your browsing experience, you can find it here: https://bitcointalk.org/index.php?topic=973843.0 (Updated 2015-05-31)

Note that a there can be more than one nonce that will solve a block, so even if the nonce that ends up in the block is not the one you submitted, it doesn't mean that your nonce wouldn't have worked too. It is also possible that whoever did solve the block included different transactions than you would have. If there is ANY change at all in the included transactions (even the order that they are included) or the header of the the block, then the nonce that solves the block will be different as well.

You really can't look at the solved block to determine if one of your submitted nonces match the nonce that eventually makes it into the block. It should be pretty easy though to demonstrate that a nonce you provided would generate a block hash that meets the necessary difficulty.

What makes you think the pool is trying to keep you from solving blocks?

The quality of posts has dropped to such a low level that all users who are participating in a paid signature campaign are added to my ignore list. If you'd like a copy of the list to improve your browsing experience, you can find it here: https://bitcointalk.org/index.php?topic=973843.0 (Updated 2015-05-31)

Note that a there can be more than one nonce that will solve a block, so even if the nonce that ends up in the block is not the one you submitted, it doesn't mean that your nonce wouldn't have worked too. It is also possible that whoever did solve the block included different transactions than you would have. If there is ANY change at all in the included transactions (even the order that they are included) or the header of the the block, then the nonce that solves the block will be different as well.

You really can't look at the solved block to determine if one of your submitted nonces match the nonce that eventually makes it into the block. It should be pretty easy though to demonstrate that a nonce you provided would generate a block hash that meets the necessary difficulty.

What makes you think the pool is trying to keep you from solving blocks?

There seems to be a % over a long period of time... problem is, it is not a random % as you would expect, and the site shows stales as 5 and 3 dups, but the figures don't add up.

I can "rip out" a section of a python miner and use an ASIC to validate them as they bounce, but I'd rather get a 3rd party validationmaybe its some sort of bug in the FPGA code, due to CLK slippage.

1. Hashes are non-reversible, a hash cannot be turned into data2. You can look up the contents of a solved block and see the nonce, since it is a readable part of a block's contents:http://blockexplorer.com/rawblock/000000000000003c74f147f11e68ad5283efbad7796e5774836e75e7ed3340d13. Other block content is specific to the pool and constantly changing in blocks, such as the coinbase and the generate payout tx address.4. It is trivial to determine if you solved a block or produced a valid share - if the hash of the share you are submitting is lower than the target, then it is a block solve. You can alter your mining software to record all shares you submit, the published hash of a solved block will be the same as your submission if you found one.5. You can alter mining software to record the input data that produced a valid share, and re-hash it to verify it works. A pool will have different criteria than just it is a hash, they need to verify a share is still a valid block solve for the current block, and the coinbase, rollntimestamp is reasonable, and that it is work that was requested of you.5. What is the problem?