[40+ PH] SlushPool (slushpool.com); World's First Mining Pool

[Mudbankkeith]

The usual reason for low payouts is down to the internet deciding to run slow.

My normal connection speed is approx 8meg

I can be watching an online film and the video is reporting 4.1meg. My miners are also working normally.

The video feed will suddenly freeze and report speeds of 0.1meg(slower than old dial up).  
If the freeze lasts more than a few mins and a block is found during the freeze time, then the payout for that block is low. My miners are still running apparently normally.

If I were to monitor the miner carefully at this time (very difficult with 80+ devices) I would probably see an increase in Reject and Stale results, but within a few mins this would be lost again in the background.

Slush is paying more for the freshest calculations and much less for the older results.
So if the hashes are not getting to the pool before the block is found, then they will not count towards the payout. (The pool thinks you are skipping).
Late arrivals are not counted.

I agree but I also think there is a chance "late arrivals" may very well count towards the next block. I will see a low payout and the next block sometimes will make up for it as I thought the late shares get credited towards it?

Quote from Slush's Pool:-

How does bitcoin pool work?

Our server gives users blocks of very low difficulty to solve. Each solution found is registered as one 'share'. Occasionally, a solution will happen to also meet the full-strength difficulty requirements of the Bitcoin network, resulting in a successful 25 BTC minting.

This 25 BTC is divided among all of the users that contributed to that round, weighted by the number of shares that they earned. Therefore, the reward earned by a given user is given by the following formula:

(25 BTC + block fees - 2% fee) * (shares found by user's workers) / (total shares in current round)
Shares do not carry over from one round to the next. When the pool mine a block, only users who worked on that block are rewarded, and only for work they did on that block. This is an unavoidable consequence of the way that Bitcoin mining in general works.

Late arrivals go in the bin

[1475192807]

1475192807

[1475192807]

1475192807

[1475192807]

1475192807

[Tazza]

seems like a big issue if all these numbers are correct.  Some are getting heavy/double paid and some are getting far less.  This did happen a day or so ago and after conf it was fixed. Time will tell.

This is exactly why I'm not all that concerned. I've only been on Slushes pool for a few months... But read right back to the beginning and there have always been postings every couple of pages asking "what happened to my payout in round x" but it seems these inevitably sort themselves out.  FWIW was a dodgey one for me as well:

21027    2013-12-02 23:04:34    5:49:17    1993521951    12274    0.00000172    272726    25.00902152    confirmed

[Mudbankkeith]

Some of it went here

21028   2013-12-02 23:33:20   0:28:46   166468331      18121   0.00259365   272729   25.29332793    confirmed
21027   2013-12-02 23:04:34   5:49:17   1993521951  216591   0.02075325   272726   25.00902152    confirmed
21026   2013-12-02 17:15:17   0:42:40   241981189      25581   0.00267538   272690   25.19850076    confirmed

[harry1]

21028   2013-12-02 23:33:20   0:28:46   166468331   35443   0.00517607   272729
21027   2013-12-02 23:04:34   5:49:17   1993521951   439645   0.00006616   272726
21026   2013-12-02 17:15:17   0:42:40   241981189   52780   0.00474667   272690

Same Problem
peanuts but not ok

[Tazza]

since I noticed that there are quite a few people making comments about not getting rewards even though they know their miners have been hashing away, say in a situation like that, if the pool ends up completing the block, but most everyone's stats shows "none" for rewards, then where do the 25 bitcoins go? I'm sure someone must end up with them, right?

Two different scenarios really mate. The first is when people on here get their knickers in a knot over stats showing "none" or zero after processing is completed, but still taking 15 mins or so until it will show the correct reward. This is normal in my experience and no Btc disappear.
The second, which admittedly is one that should probably be looked into even though it too normally sorts it self out, are the rounds showing a lower reward than normal for some people but a higher reward than normal for others.

So one last rookie question. If I do decide to get more into this, obviously continuing mining with my CPU will NEVER be profitable. At about what hash rate have most of you seen the BTC start rolling in? I'm not delusional enough to think that I will ever make a fortune off of this, but I wouldn't mind seeing at least a couple hundred bucks or so over the course of a month or three in order to make it feel like my efforts are not in vain. Right now my meager 0.00000142 BTC just ain't cutting it! 

Depends on how much you want to outlay initially really. There is no hard and fast answer. You could fork out a grand or so today for a few 100Ghash) machines but you're not going to get them for 3 or 4 months minimum - who knows what the difficulty or return will be then. On the other hand to get anything in hand immediately you are looking at ridiculous mark ups. Block eruptors that were not long ago around $15 on Au Ebay are now going for over $60 each (335Mhash). I wish the media kept their traps shut about the rise of btc it would have made things much cheaper

[gourmet]

21027 and 21033 need recalculations, my reward is halved again.

My reward for round 21027 is 1/100 of the usual one. But it has been confirmed already... :-(

[Kaos116]

With block 21027 now being confirmed, is this going to make it tougher to fix?

What happens to those that got extra?

 If I had been one of those that got extra, it would have pushed me over my payout threshold. It would have paid out, but when (or if) it went back to fix it, there would not be enough in my rewards to give back.

[FalconFly]

21028    2013-12-02 23:33:20    0:28:46    166468331    485    0.00006462    272729    25.29332793    confirmed
21027    2013-12-02 23:04:34    5:49:17    1993521951    6010    0.00000096    272726    25.00902152    confirmed
21026    2013-12-02 17:15:17    0:42:40    241981189    966    0.00010627    272690    25.19850076    confirmed

Annoying indeed...
I have no issue with the regularly varying score (which always occurs to me despite having a 50MBit pipe with extremely constant connection quality and no significant change neither to total Slush Hash power or my own), but I think that "anti-pool" hopping routine is overly punishing Shares that come to the server just a few seconds late.
I mean when a round is i.e. 10 hours and I contributed @ full average speed for 9h 59m with the final shares somehow being a tad delayed (despite my GUIminers showing no evidence of any delay/problem whatsoever), that shouldn't be punished so hard.
Plus, I also see it overnight when there's absolutely no other traffic using my Internet connection, it's 100.0% mining only.

Just stopping miners (which ran days uninterrupted 24/7) for only 10 seconds (!) to change some settings is making the rewarded BTC taking a considerable and unproportional hit, IMHO that's not okay and making me considering to at least try other pools.
In the end results, their additional fees become insignificant when compared to the losses I see here everyday due to that extremely aggressive scoring/time vs. reward reduction routine :/
Additionally because of being new around here, such events always leave a nagging doubt that this behaviour is systemic and intentionally scooping off small fractions of BTC Rewards per participant. No proof for that of course but the doubt remains (especially because now big money is involved every day), those repeating small issues don't quite reduce these doubts :/

Just my 2 cents from a low profile miner, I'd probably be much more unhappy if I had some big THash rigs rolling and seeing the same...

[RaveOn911]

Just checked and mine is the same

21029    2013-12-03 00:03:45    0:30:25    174346782    9513    0.00137131    272735    25.00901001    confirmed
21028    2013-12-02 23:33:20    0:28:46    166468331    8865    0.00120803    272729    25.29332793    confirmed
21027    2013-12-02 23:04:34    5:49:17    1993521951    104048    0.00001684    272726    25.00902152    confirmed
21026    2013-12-02 17:15:17    0:42:40    241981189    12256    0.00128974    272690    25.19850076    confirmed

[bobsmoke]

21027 and 21033 need recalculations, my reward is halved again.

My reward for round 21027 is 1/100 of the usual one. But it has been confirmed already... :-(

+1 - The same here

[googoofish]

21028   2013-12-02 23:33:20   0:28:46   166468331   50525   0.00793538   272729   25.29332793    confirmed
21027   2013-12-02 23:04:34   5:49:17   1993521951   610368   0.00008752   272726   25.00902152    confirmed
21026   2013-12-02 17:15:17   0:42:40   241981189   72784   0.00803961   272690   25.19850076    confirmed

I was one of the unlucky ones also 

[MonocleMan]

21029   2013-12-03 00:03:45   0:30:25   174346782   7072   0.00103284   272735   25.00901001    confirmed
21028   2013-12-02 23:33:20   0:28:46   166468331   6588   0.00090089   272729   25.29332793    confirmed
21027   2013-12-02 23:04:34   5:49:17   1993521951   80006   0.00001236   272726   25.00902152    confirmed
21026   2013-12-02 17:15:17   0:42:40   241981189   9828   0.00094357   272690   25.19850076    confirmed
21025   2013-12-02 16:32:37   10:39:33   3490407934   144560   0.00099827   272687   25.06788253    confirmed

+1 for me as well

[nybbler905]

great... i got nada due to no power here for that round.....
[EDITED TO ADD]
lost power at around 3rd hour of the 5:49:17 and didn't get it back on until part way in to the 2nd round after...

0.00000002 is still more than i'd expect for doing 3hrs of 5+ hour hashing ( assuming my clocks are correct now )

[MrTeal]

Round 21027 has the same 1% of the expected payout that most other people here are seeing for me as well. I don't believe that it is a connection issue on my end, as my number of shares / total shares is the same as every other round.

Hopefully Slush fixes it, he's usually excellent about such things.

[CathalG]

How do i do merged mining on this pool... And what are the coins i can merge with?

[Current C]

So im not the only one getting hosed on multiple blocks.

is there any correction being performed or are we just expected to accept that its the cost of using slushes pool?

[5120-01-518-6126]

How do i do merged mining on this pool... And what are the coins i can merge with?

Slush's pool doesn't do merged mining anymore.

[bigbeninlondon]

Anyone else seeing really low reported hashrate?  I'm pushing 10 GH/s and pool is reporting 2 GH/s.  Weird...

[LockUnlock]

Anyone else seeing really low reported hashrate?  I'm pushing 10 GH/s and pool is reporting 2 GH/s.  Weird...

Nope it's doing fine on my end

[Kaos116]

Anyone else seeing really low reported hashrate?  I'm pushing 10 GH/s and pool is reporting 2 GH/s.  Weird...

Nothing abnormal. The start of a new block my rate drops about half but recovers quickly.

On a side note, I still haven't seen a correction to 21027 yet.