I think the problem is the lack of knowledge of the principals of pool mining.
It would be quiet long to describe everything here.
First you have to know what a hash function does, then it will make sense.
difficulty: simply said it's equivalent of the number of the leading zero values in the hash result. More zeros mean higher difficulty, because the set of valid values is decreasing with more zeros (like a shrinking target when shooting)
share: a solution proposal for the current block (nounce is the key here, DYOR)
worker difficulty: the difficulty limit of your pool worker, if you find a share with a difficulty higher than that, it's sent to the pool.
network difficulty: the difficulty calculated from the hashrate of the entire network.
share difficulty: the actual difficulty of the found share. Only a share with a difficulty higher than the network diff is accepted as a valid block candidate.
So for you question (whats your share diff) the answer is that share diff is calculated straight from the leading zeros of your found hash.
The miner program only shows shares that has difficulty higher than you current worker diff.
If you are mining in a pool that's using dynamic worker diff you can see a lot of shares in the first few minutes while the pool is adjusting your worker diff according to your hashrate.
Thanks for the answer, but ....
See:
There is a miner's log that writes to me:
ETH: - SHARE FOUND - (GPU 1) (
DIFF: 17.799G)
I want to understand how the shares are calculated difficulty these
17.799GI understand that I need to look at the parameters that are passed in eth_getWork and eth_submitWork - or how?