[4+ EH] Slush Pool (slushpool.com); Overt AsicBoost; World First Mining Pool

[animan]

Hello,

New to bitcoin mining. Have been mining slush's pool for the last 3-4 days.

I am not getting the payout on one transaction, block # 237634. I had 1027 shares, but the BTC payout is 0.0.
Can someone please explain why this would happen, or if it could possibly be an error in the system.
Thanks.

18183 2013-05-24 06:47:53 1:48:51 15038629 236 0.00083160 237647  25.28940000 confirmed 
18182 2013-05-24 04:59:02 5:59:04 49271773 1027 0.00000000 237634  25.43307428 confirmed 
18181 2013-05-23 22:59:58 2:17:42 18432045 528 0.00079536 237593  25.27100000 confirmed 

Animan - there seems to be something wrong with your miner or your internet connection. Looking at the speed of your mining - shares per minute:
18181: 3.854spm, but then going a bit lower in 18182: 3.435spm and then even lower in 18183: 2.185spm

Presuming your normal speed is 3.854spm you should've had 1152 shares for round 18182. Or you're short 125 shares, or at that speed - you haven't been mining for 33 minutes. Now, given that your next round is even lower, I'd say you probably stopped mining during the last 33min of round 1152 and that's why you didn't get anything for that block.

Presuming the same speed, you started mining at some point and you kept mining for the last 61minutes of round 18183, and that's why you got a good reward for that block.

With minor edits - here is something I posted earlier that hopefully sheds some more light:

You need to understand a bit more about how Slush's pool works and you (and many other) get confused with the PPS (pay-per-share) concept. Slush's pool is not a PPS one.

For a start you can look at the detailed description of how it works is on the pool's home page - look for a text in big yellow letters that says "How does bitcoin pool work?".

In essence each share gets a "score". The score is highest at the round end, and earlier shares get lower scores. The older the share the lower the score. And that progression is not linear but exponential, so score goes down to almost zero very quickly. From observations I think the cut-off is about an hour - for shares older than an hour you get absolutely no score.

Thanks for the explanation. I am not sure if I temporarily lost internet connection during that period. But getting 0 reward after cranking out 1027 shares just does not make sense to me

[1714171811]

1714171811

[1714171811]

1714171811

[1714171811]

1714171811

[1714171811]

1714171811

[1714171811]

1714171811

[nottm28]

Thanks for the explanation. I am not sure if I temporarily lost internet connection during that period. But getting 0 reward after cranking out 1027 shares just does not make sense to me

Let me introduce - there's a guy on here who has done some of the most serious analysis I have seen

http://organofcorti.blogspot.com/2012/04/41-slushs-pool.html
http://organofcorti.blogspot.com/2012/08/42-slushs-score-method-and-miner.html
http://organofcorti.blogspot.com/2012/09/43-slushs-score-method-and-miner.html

Makes for a good read...

[oroboras]

I have 3.2 and 2 avalon usb's (europe order) on the way. (I wont mention my BFL order for fear of turning slush's thread into a slanging match)

LOL I have 10 of the USB's coming from A+C also.... so I guess when they get here I will be closer to 4GH/S

Nice. No slanging from me though - I have 32GH/s of BFL on order, to compliment my 1GH/s now, and if the bank smiles on me, 700GH/s of KnCMiner to be ordered.
I will know in a couple of weeks if I will get to join the big boys or not.

[EasyQuest]

Calculation error?

18219   2013-05-25 23:31:47   0:33:15   4923475   4003   0.02103287   237930   25.21042000    85 confirmations left
18218   2013-05-25 22:58:32   0:25:35   3754815   3039   0.01185884   237928   25.00650000    83 confirmations left
18217   2013-05-25 22:32:57   1:00:46   8928761   7448   0.02057664   237921   25.47807000    76 confirmations left

I checked and none of my miners were down......

I notice the scoring was bugged during mining operation.

Estimated reward tanked and then recover over a period amount of time. I have seen this before which then causes these annoying reward errors people been talking about.

[5120-01-518-6126]

Payout for round 18218 -- ongoing miscalc problem, low transaction fees, or just variance?


18219 --2013-05-25 23:31:47 -- 0:33:15 -- 4923475 -- 2350 -- 0.01151355 -- 237930 -- 25.21042000 -- 84 confirmations left
18218 --2013-05-25 22:58:32 -- 0:25:35 -- 3754815 -- 1814 -- 0.00691102 -- 237928 -- 25.00650000 -- 82 confirmations left
..
18216 --2013-05-25 21:32:11 -- 0:26:24 -- 3940018 -- 1850 -- 0.01299966 -- 237915 -- 25.07852000 -- 69 confirmations left
...
18213 --2013-05-25 20:25:33 -- 0:28:52  -- 4289177 -- 2142 -- 0.01138243 -- 237903 -- 25.51505422 -- 57 confirmations left

[bspurloc]

Calculation error?

18219   2013-05-25 23:31:47   0:33:15   4923475   4003   0.02103287   237930   25.21042000    85 confirmations left
18218   2013-05-25 22:58:32   0:25:35   3754815   3039   0.01185884   237928   25.00650000    83 confirmations left
18217   2013-05-25 22:32:57   1:00:46   8928761   7448   0.02057664   237921   25.47807000    76 confirmations left

I checked and none of my miners were down......
I notice the scoring was bugged during mining operation.
Estimated reward tanked and then recover over a period amount of time. I have seen this before which then causes these annoying reward errors people been talking about.

18218   2013-05-25 22:58:32   0:25:35   3754815   967   0.00367753   237928   25.00650000
18217   2013-05-25 22:32:57   1:00:46   8928761   2242   0.00672909   237921   25.47807000
18216   2013-05-25 21:32:11   0:26:24   3940018   931   0.00552174   237915   25.07852000

Yeah 237928 had issues. I did not have connection issues and that is all I will say about that.
Something calculated wrong on that block. topic done.

[rsbriggs]

Is some issue with score not resetting to zero at start of 18221 round or problem with estimated?  
Estimated score for this round being about 1/40  normal, .00010 instead .0044 ever since starting.

[autonomous42]

Is some issue with score not resetting to zero at start of 18221 round or problem with estimated?  
Estimated score for this round being about 1/40  normal, .00010 instead .0044 ever since starting.

And my estimate is about 1700x normal. Oops.

[bspurloc]

Is some issue with score not resetting to zero at start of 18221 round or problem with estimated?  
Estimated score for this round being about 1/40  normal, .00010 instead .0044 ever since starting.

Ah. I see it is happening with the present block. I'm back up to almost 50% of normal as it slowly fixes itself.

[rsbriggs]

Is some issue with score not resetting to zero at start of 18221 round or problem with estimated?  
Estimated score for this round being about 1/40  normal, .00010 instead .0044 ever since starting.

Ah. I see it is happening with the present block. I'm back up to almost 50% of normal as it slowly fixes itself.

Slowly fixing self little bit over last 1/2 hour.  Maybe back close to normal if block going another 1/2 hour or longer.

[EasyQuest]

Weird how this has been happening for more than a month and just these past two weeks it has been happen more often than normal.....

[Uliss]

Now:
Approx. cluster performance (30 min average):   10433.954 Ghash/s
Current server load (60 sec average):   246 getwork/s

18220    2013-05-26 02:26:32    2:54:45
Current round duration:   2:49:06

Yesterday - 450-500 getwork/s, found 25 blocks  

What server?
----------------

BitMinter now:

[rassalas]

Out of curiosity - is your hashing speed around 3.5-3.6GH/s?

I'm only running about 2.7GH/s hardware can probably hit closer to 3GH/s but I have cooling issues that need to be resolved.

maths not my strongsuit.... kudos nottm28

Entering new workers with same credentials at the alternate serve did the trick.  I did have to experiment with syntax to get valid credential
submission,  my poor memory or confusion with other pool standards...   not important once I sorted it out Stratum server is working fine.   

I do have one annoying factor, Stratum is 4 characters longer then api so now my old worker names are too long to display well in a cgminer terminal
that is each pool takes two lines, for my current name.wrkr.  I could rename but last time I did that I lost some shares.

[minerapia]

Now:
Approx. cluster performance (30 min average):   10433.954 Ghash/s
Current server load (60 sec average):   246 getwork/s

18220    2013-05-26 02:26:32    2:54:45
Current round duration:   2:49:06

Yesterday - 450-500 getwork/s, found 25 blocks  

What server?
----------------

BitMinter now:

Amount of getworks per sec is totally meaningless, its only 100-200 Ghs from total of 10401.213 Ghash/s.

Also comparing couple of few last blocks to bitminter is worthless also, they ran into streak of luck after being unlucky for a moment. Bitminter has invalid block issues still running (pool admins havent updated I guess).

[Uliss]

Amount of getworks per sec is totally meaningless, its only 100-200 Ghs from total of 10401.213 Ghash/s.

Also comparing couple of few last blocks to bitminter is worthless also, they ran into streak of luck after being unlucky for a moment. Bitminter has invalid block issues still running (pool admins havent updated I guess).

I noticed that the more getworks, the more blocks.

Sorry, this is the Google Translator...

[minerapia]

Amount of getworks per sec is totally meaningless, its only 100-200 Ghs from total of 10401.213 Ghash/s.

Also comparing couple of few last blocks to bitminter is worthless also, they ran into streak of luck after being unlucky for a moment. Bitminter has invalid block issues still running (pool admins havent updated I guess).

I noticed that the more getworks, the more blocks.

Sorry, this is the Google Translator...

Its about luck, finding block is lottery. Sometimes you have more luck and you find more blocks. Only thing that really matters is the Ghs because eventually luck is evened out.
Amount of getworks/s is just old remnant regarding old getwork protocol. 98% of the pool is using stratum now.

[bspurloc]

Is some issue with score not resetting to zero at start of 18221 round or problem with estimated?  
Estimated score for this round being about 1/40  normal, .00010 instead .0044 ever since starting.

Ah. I see it is happening with the present block. I'm back up to almost 50% of normal as it slowly fixes itself.

Slowly fixing self little bit over last 1/2 hour.  Maybe back close to normal if block going another 1/2 hour or longer.

It is happening again. this is a NEW problem that I have not seen over the few weeks. but of course I am just a complainer and shouldnt point out something like this. In the past, I have seen this happen on 2+ hour blocks and fix itself over 15minutes. this is now happening in blocks 15+ minutes and taking 30+ minutes to fix itself. I've never noticed this fix itself during confirmation because the algorithm decided the shares were decayed

er, it was fixed now just reset back to 0 again.... "0.00001862 BTC" nothing to see here move along, all is well...

-----
3minutes into this new block estimated reward 0.00000001 BTC I have 130 shares in 2.65gh/s. there is no way the decay algorithm is working right within that time period and my hashrate. If I were having connection issues I would not be able to be at 130 shares

[desired_username]

This is the first anomaly I have got:



I didn't have disconnect or miner restart.

Any explanation why this particular block reward was so low compared to all the others?

[Lucko]

Block 18222, 18223 and 18218 with reset issues? And block 18220 with posible reset issues. I know I should moved miner off this pool yesterday. Why I didn't(OK I know why, I was waiting for end of block and then forgot)... Slush it is time to fix this... I hate to look at every block with microscope...

EDIT:

This is the first anomaly I have got:



I didn't have disconnect or miner restart.

Any explanation why this particular block reward was so low compared to all the others?

Reset issues. If Slush is around it will get fix if not you are out of luck... And you will probably see same for block 18220, 18222 and 18223 unless you are one of the lucky that gain because of a reset.

[vs3]

This is the first anomaly I have got:



I didn't have disconnect or miner restart.

Any explanation why this particular block reward was so low compared to all the others?

Yep, and if you look up on this very page (just about a dozen posts before yours) you'll notice that block 18218 has already been reported as being problematic. My point is - we already know that. And we're already asking the same question - why?

From what we've seen so far - everyone got about half of the payout they usually/should get. Unfortunately it seems only Slush can tell us what's going on.

Slush - if you read this please and actually pretty please - could you shed some light?