Should accepted shares\*pool diff equal EXACTLY accepted diff shares?
-
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 share63+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? -
maybe vardiff causes it to optimize until you get it exactly.
also over time even though it is random the individual shares add up.
-
[quote name=“zerodrama” post=“13649” timestamp=“1371042980”]
maybe vardiff causes it to optimize until you get it exactly.also over time even though it is random the individual shares add up.
[/quote]so if i dont quit the mining right when i get a accepted share update, then i would lose any accepted difficulty 1 work shares that were over the accepted shares*pool difficulty right?
-
accepted share are the accepted submission and the diff is the multiplier of the base unit of work. the diff is just to prevent submitting a very large number of work proof
so yes your accepted share * pool diff should be your shared difficulty.
similar to block when you find a 31 diff on the pool it should on average takes 31 more time then finding a base unit of work. Diff is different from one miner to the other in var diff you get a pool diff. a good diff with var diff should give you a diff that provide regularly a good average of the work done over some hour without submitting constantly low diff share or not submitting enough share to get a representative average. ()
when a block is found all shared difficulty are added for all miner in the pool. so your shared diff/all miner shared diff give your part of the work done on the block.
note: the share diff don’t care the real difficulty of what you fond, it just care it’s over the diff and assign the diff to it so you get a work unit done that is at least the pool diff
