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

[dlefevre]

I got a little less than double on that round as well...

21029    2013-12-03 00:03:45    0:30:25    174346782    28913    0.00408863    272735    25.00901001    92 confirmations left
21028    2013-12-02 23:33:20    0:28:46    166468331    29568    0.00451569    272729    25.29332793    86 confirmations left
21027    2013-12-02 23:04:34    5:49:17    1993521951    352054    0.00842425    272726    25.00902152    83 confirmations left
21026    2013-12-02 17:15:17    0:42:40    241981189    42646    0.00421066    272690    25.19850076    47 confirmations left
21025    2013-12-02 16:32:37    10:39:33    3490407934    645818    0.00465805    272687    25.06788253    44 confirmations left

[1713895436]

1713895436

[1713895436]

1713895436

[1713895436]

1713895436

[bigbeninlondon]

21027    272726   2013-12-02 18:04:34   00:03:35:56   00:05:49:17   0.00000637   78

Low round for me too.

[LockUnlock]

Same here:
21027   2013-12-02 23:04:34   5:49:17   1993521951   10649   0.00000159   272726   25.00902152    72

Is this an issue?

[xZork]

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.

[Tiennou74]

21027   2013-12-02 23:04:34   5:49:17   1993521951   512952   0.00056257   272726   25.00902152    41 confirmations left
21026   2013-12-02 17:15:17   0:42:40   241981189   59201   0.00557387   272690   25.19850076    5 confirmations left
21025   2013-12-02 16:32:37   10:39:33   3490407934   894361   0.00593625   272687   25.06788253    2 confirmations left

same here

[ma_bit]

21027    272726   2013-12-02 18:04:34   00:03:35:56   00:05:49:17   0.00000637   78

Low round for me too.

+1

[macsheadroom]

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

[Searing]

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

ditto

[aurel57]

Same here,

21027    2013-12-02 23:04:34    5:49:17    1993521951    44587    0.00000631    272726    25.00902152    86 confirmations left

Mind sending some of that this way aurel?

I am usually on the short end and only a few times have had the wrong amount go it this direction but those few times it has always been readjusted as I am sure that is what will happen this time.

[Sir Alan]

I hate being a "me too", but...

21027  2013-12-02  23:04:34  5:49:17  1993521951  42217  0.00000604  272726  25.00902152  14 confirmations left

as compared to

21013  2013-12-01  12:54:49  6:11:57  1958796234  44657  0.00054740  272483  25.12828530  confirmed

[Mudbankkeith]

21010   2013-12-01 03:31:42   1:59:40   639039598       75992   0.00326874   272410   25.14099989    confirmed
21009   2013-12-01 01:32:02   0:04:19   22915150         2918     0.00317004   272399   25.03550690    confirmed
21008   2013-12-01 01:27:43   0:50:06   265077329        31730   0.00294244   272398   25.02827623    confirmed
21007   2013-12-01 00:37:37   7:48:38   2147483647   293119   0.00288164   272385   25.20690867    confirmed
21006   2013-11-30 16:48:59   0:47:42   251032842        29358   0.00278538   272318   25.03404462    confirmed

Round 21007 paid normal for me.

My biggest concern is that it was nearly 8 hours.
Blocks are supposed to be an average of 10 mins.
The average here is more like 2 hours. That is 12 times slower than average.(over the last 30 rounds it was 65hours 31mins, that is 2hours and 11mins per block)

I would like to mine on the other pool that is running at 12 times faster than the average. Does anyone know where it is?

[aurel57]

21010   2013-12-01 03:31:42   1:59:40   639039598       75992   0.00326874   272410   25.14099989    confirmed
21009   2013-12-01 01:32:02   0:04:19   22915150         2918     0.00317004   272399   25.03550690    confirmed
21008   2013-12-01 01:27:43   0:50:06   265077329        31730   0.00294244   272398   25.02827623    confirmed
21007   2013-12-01 00:37:37   7:48:38   2147483647   293119   0.00288164   272385   25.20690867    confirmed
21006   2013-11-30 16:48:59   0:47:42   251032842        29358   0.00278538   272318   25.03404462    confirmed

Round 21007 paid normal for me.

My biggest concern is that it was nearly 8 hours.
Blocks are supposed to be an average of 10 mins.
The average here is more like 2 hours. That is 12 times slower than average.(over the last 30 rounds it was 65hours 31mins, that is 2hours and 11mins per block)

I would like to mine on the other pool that is running at 12 times faster than the average. Does anyone know where it is?

Its all in proportion to the hash rate of the pool. Blocks are found on average 10 mins on the network not per pool. The larger the pools may find more blocks but you will receive less per block as you would in a smaller pool. I have tried 4 different pools and like slush's pool best.

EDITED: But even the big pools will get stuck on a long block... its all about the luck which over a long period should even out.


Block #21035 which we just found was done in 55 seconds!

[Sir Alan]

I wonder how many miners who hop to a pool which has just had a good run of luck will also go out and buy a lottery ticket using last week's winning numbers?

[aurel57]

I wonder how many miners who hop to a pool which has just had a good run of luck will also go out and buy a lottery ticket using last week's winning numbers?

LOL I agree!

I tried some different pools to see how they compared to slush's. They all have their pro's and con's but find this pool to be easy to understand compared to others with the chance of having goods days when the luck is good.

[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.

[aurel57]

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?

[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

[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