wizstats
wizstats copied to clipboard
wizkid057
Position in Payout Queue Reads Constant 0.0000
Estimated Position in Payout Queue Approximately 0.00000000 BTC remaining to enter payout queue. Maintaining your 3 hour hashrate average, this will take at least another a few seconds at current network difficulty of
Reads this constantly regardless of whether a block is solved and not sure if the payout is working at all.
When you go to view the payout queue, it is totally empty?
Something wrong. It appears a file was changed as the payout queue link is in a different place to where it was earlier today.
Not a bug in stats really, happens when the reward system pauses for one or more reasons pending manual review (which happened about an hour ago).
The stats should probably handle it more gracefully, though.
Ok thanks for the clarification :) On 17/10/2013 10:42 PM, "wizkid057" [email protected] wrote:
Not a bug in stats really, happens when the reward system pauses for one or more reasons pending manual review (which happened about an hour ago).
— Reply to this email directly or view it on GitHubhttps://github.com/wizkid057/wizstats/issues/38#issuecomment-26497302 .
So when I get this message:
Estimated Position in Payout Queue
Approximately 0.00000000 BTC remaining to enter payout queue. Maintaining your 3 hour hashrate average, this will take at least another a few seconds at current network difficulty of 4,250,217,919.87.
7:57am EDT today
and then I reload the browser a few minutes later:
Estimated Position in Payout Queue
533.78008269 BTC are ahead in queue, putting this user's payout after a 21 block delay.
7:59am EDT today
Which one is right? It is a pretty big tease to show that payout is a few seconds away and then it looks like I have moved to the back of the line! This happens quite often for me. It seems like every payout I see this pattern at least one time before it finally pays out for real.
First, It never said you will get a payout in a few seconds. It said you will enter the queue in a few seconds.
The stats are not completely real-time and rely on data pushed from the core pool servers. If this data gets stale, due to load usually, then it might take the stats a few moments to receive fresh data.
In any case, your actual position in the payout queue isn't effected by what the stats may or may not display about it. It tries to be as informative as possible, but might not always have all of the information needed, hence the issue open here.