Author

Topic: Should my accepted shares*pool diff equal EXACTLY the accepted difficulty1 share (Read 4232 times)

hero member
Activity: 526
Merit: 500
Its all about the Gold
Sounds like you're confusing actually mining higher difficulty shares with calculating higher difficulty shares.

You will need to do X number of hashes to solve a difficulty 1 block, that number X will vary. So the time it takes for you to submit a diff 1 share will vary from share to share.

The same is true for a diff 8 share, except that there will be a greater amount of variance due to the greater difficulty.

When you calculate submitted shares that is looking back over what has been submitted, and so a calculation of the equivalent value will of course match.

see those stats above? that is direct from the cgminer program to this post. They are exactly the same in other words , for however many accepted difficulty 1 shares you get it will be divided by the pool difficulty and that becomes your accpeted shares---in other words --quit the mining program before getting a  accepted share will lose all difficulty shares even if there was enough for a accepted share before cgminer did its scan log.
newbie
Activity: 42
Merit: 0
Wow this is a weird problem
hero member
Activity: 602
Merit: 500
Sounds like you're confusing actually mining higher difficulty shares with calculating higher difficulty shares.

You will need to do X number of hashes to solve a difficulty 1 block, that number X will vary. So the time it takes for you to submit a diff 1 share will vary from share to share.

The same is true for a diff 8 share, except that there will be a greater amount of variance due to the greater difficulty.

When you calculate submitted shares that is looking back over what has been submitted, and so a calculation of the equivalent value will of course match.
hero member
Activity: 526
Merit: 500
Its all about the Gold
i am seeing something odd here about my accepted shares that is consistent on litecoins and feathercoins mining. My understanding according to the readme of cgminer 3.1.1 is the accepted difficulty shares is how many difficulty 1 shares you have mined. And that your accepted shares is the number of shares equal to or above the pool difficulty. My discovery for 3 days worth of stats is this:

feathercoin mining: pool difficulty 31 cgminer shows me 3844 accepted difficulty shares and 124 accepted shares
                                         124*31=3844
litecoin mining: pool difficulty 64 cgminer shows me 640 accepted difficulty shares and 10 accepted shares
                                          64*10=640
feathercoin mining: pool difficulty 31 cgminer shows me 1953 accepted difficulty shares 31 rejected difficulty share and 63 accepted shares and 1 rejected share

                                         63+1=64*31=1984  1953+31=1984

so my confusion is , ironically im getting EXACTLY an amount of accepted shares based on getting so many difficulty 1 shares divided by the pool difficulty to the tee?

meaning im getting no extra shares of difficulty 1 but an exact number to meet the equation of :

Q: Why don't the statistics add up: Accepted, Rejected, Stale, Hardware Errors,
Diff1 Work, etc. when mining greater than 1 difficulty shares?
A: As an example, if you look at 'Difficulty Accepted' in the RPC API, the number
of difficulty shares accepted does not usually exactly equal the amount of work
done to find them. If you are mining at 8 difficulty, then you would expect on
average to find one 8 difficulty share, per 8 single difficulty shares found.
However, the number is actually random and converges over time, it is an average,
not an exact value, thus you may find more or less than the expected average.

that is a copy and paste straight from the readme file on github.

according to that my accepted difficulty shares should be not exactly my accepted shares divided by the pool difficulty --could it be exact  well yes it could but EVERY TIME?     
the number of shares that are accepted by cgminer were also accepted by pool website.
am i missing something here?
Jump to: