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

[tommymal83]

yes i have had 2 very low points payouts today blocks 22106 and 22105.....both 50%
oh what i normally get......hopefully slush will correct this error....lol 

[TrytoHex]

I submitted a ticket...

[Alexiandar]

yes i have had 2 very low points payouts today blocks 22106 and 22105.....both 50%
oh what i normally get......hopefully slush will correct this error....lol 

Same here, 50% of normal payout for 22106

[FUBUKY]

yes i have had 2 very low points payouts today blocks 22106 and 22105.....both 50%
oh what i normally get......hopefully slush will correct this error....lol 

Same here, 50% of normal payout for 22106

my 200% more payout for 22106

in other block is normal payout

[Mudbankkeith]

yes i have had 2 very low points payouts today blocks 22106 and 22105.....both 50%
oh what i normally get......hopefully slush will correct this error....lol 

Same here, 50% of normal payout for 22106

my 200% more payout for 22106

in other block is normal payout

sounds like you got the jackpot!

[FUBUKY]

yes i have had 2 very low points payouts today blocks 22106 and 22105.....both 50%
oh what i normally get......hopefully slush will correct this error....lol 

Same here, 50% of normal payout for 22106

my 200% more payout for 22106

in other block is normal payout

sounds like you got the jackpot!

normal payout is 0.00703204, in block 22106  first  0.02003204 down to payout 0.01350420

[Skydaddy]

yes i have had 2 very low points payouts today blocks 22106 and 22105.....both 50%
oh what i normally get......hopefully slush will correct this error....lol 

Same here, 50% of normal payout for 22106

my 200% more payout for 22106

in other block is normal payout

sounds like you got the jackpot!

normal payout is 0.00703204, in block 22106  first  0.02003204 down to payout 0.01350420

And I'll be dang if I can figure out how to submit a ticket with regards to this matter. Could one of the more learned members be so kind? Thanks for the efforts fellow miners!

[TrytoHex]

yes i have had 2 very low points payouts today blocks 22106 and 22105.....both 50%
oh what i normally get......hopefully slush will correct this error....lol 

Same here, 50% of normal payout for 22106

my 200% more payout for 22106

in other block is normal payout

sounds like you got the jackpot!

normal payout is 0.00703204, in block 22106  first  0.02003204 down to payout 0.01350420

And I'll be dang if I can figure out how to submit a ticket with regards to this matter. Could one of the more learned members be so kind? Thanks for the efforts fellow miners!

Go knowledgebase, in the upper left corner you click on submitted a ticket...

[Boelaap]

My reward was also "cut in half". 
I raised a ticket, and things will be sorted out as usual.

[Moria]

My reward was also "cut in half". 
I raised a ticket, and things will be sorted out as usual.

Yep 22106 was also half here..   email sent to support:)

Regards

M

[kabopar]

My reward was also "cut in half". 
I raised a ticket, and things will be sorted out as usual.

Yep 22106 was also half here..   email sent to support:)

Regards

M

My payout was lower by 18% relatively to the proportional number of my shares.  A possible explanation to this is a sudden rise in the pool hash rate towards the end of the block, which decreases the payout of all the other miners (but at the same time make a significant contribution to solving that block faster).  Let's try to illustrate this with an example: 
The pool hash rate= 1800000 GH/s  Your hash rate=200 GH/s your expected reward=0.002777778 BTC
Now assume that Miner X joined the pool with 200000  GH/s a few minutes before the end of the block, due to Slush's 'anti-hopping' algorithm, Miner X's contribution receives almost full 'weight' despite occuring towards the end of the block, so the increased short-term hash rate at the end of the block is now 2000000  GH/s, your reward drops by 10% to 0.0025 BTC.  This is not due to any 'fault' at Slush.  Actually it might have been caused by a technical or other problem on one of the competing pools, which caused briefly a massive shift of miners to Slush as their 'backup pool'.
Just my 2 mbtc.
Enjoy the recent burst of solved blocks, which more than compensates for that 'disaster'...

Cheers

[mstrongbow]

My reward was also "cut in half". 
I raised a ticket, and things will be sorted out as usual.

Yep 22106 was also half here..   email sent to support:)

Regards

M

My payout was lower by 18% relatively to the proportional number of my shares.  A possible explanation to this is a sudden rise in the pool hash rate towards the end of the block, which decreases the payout of all the other miners (but at the same time make a significant contribution to solving that block faster).  Let's try to illustrate this with an example: 
The pool hash rate= 1800000 GH/s  Your hash rate=200 GH/s your expected reward=0.002777778 BTC
Now assume that Miner X joined the pool with 200000  GH/s a few minutes before the end of the block, due to Slush's 'anti-hopping' algorithm, Miner X's contribution receives almost full 'weight' despite occuring towards the end of the block, so the increased short-term hash rate at the end of the block is now 2000000  GH/s, your reward drops by 10% to 0.0025 BTC.  This is not due to any 'fault' at Slush.  Actually it might have been caused by a technical or other problem on one of the competing pools, which caused briefly a massive shift of miners to Slush as their 'backup pool'.
Just my 2 mbtc.
Enjoy the recent burst of solved blocks, which more than compensates for that 'disaster'...

Cheers

Very well said mate.

[whispy]

Wouldn't it make more sense to reward a miner for the length of time it worked on a block?
That would deter switchers as well as not rewarding somebody who hopped in 5 minutes before a block was found.

[Moria]

My reward was also "cut in half".  
I raised a ticket, and things will be sorted out as usual.

Yep 22106 was also half here..   email sent to support:)

Regards

M

My payout was lower by 18% relatively to the proportional number of my shares.  A possible explanation to this is a sudden rise in the pool hash rate towards the end of the block, which decreases the payout of all the other miners (but at the same time make a significant contribution to solving that block faster).  Let's try to illustrate this with an example:  
The pool hash rate= 1800000 GH/s  Your hash rate=200 GH/s your expected reward=0.002777778 BTC
Now assume that Miner X joined the pool with 200000  GH/s a few minutes before the end of the block, due to Slush's 'anti-hopping' algorithm, Miner X's contribution receives almost full 'weight' despite occuring towards the end of the block, so the increased short-term hash rate at the end of the block is now 2000000  GH/s, your reward drops by 10% to 0.0025 BTC.  This is not due to any 'fault' at Slush.  Actually it might have been caused by a technical or other problem on one of the competing pools, which caused briefly a massive shift of miners to Slush as their 'backup pool'.
Just my 2 mbtc.
Enjoy the recent burst of solved blocks, which more than compensates for that 'disaster'...

Cheers

My understanding was that the calc, assuming you are mining at the time the block is found (you havent had a blip in providing hash rate etc) is  my shares / pool shares * Block Value..  for a rough calc.  (not deducting fees here)

therefore for block 22106  :-

22106  2014-05-19 16:30:41  11:23:16  18010425802  3586935   0.00206705  301575  25.10258983  97 confirmations left

which makes the calc 0.0049994

The three previous blocks using the same calc would have been :-  

22105 I get  0.0048193
22104 I get  0.0049920
22103 I get  0.0049467

All very similar and in fact almost identical to what was paid out, as were the 4 blocks post 22106

Whilst I appreciate your point about another pool jumpin in, to halve the rate paid it would have had to be approx 1872607.589 Ghash/s jumping in..  approx the rate when the block was found I believe, to drop it 50% and the your shares / total shares dont give those values, and we have also had reports of people getting double payout on that block, so something is not quite right.

This has been happening a lot since we moved to 60 minute averages, in fact one block, for me, dropped from .0048 as the calc to 0.0009 as the reward.

Whilst I appreciate your suggestion, I think something more drastic happened in this case and may be symptomatic of other blocks like this in the recent past.

I know it's not a huge issue, but when you only make 0.1 BTC a week (on average), it's a bigger deal

Regards

M

PS  dont get me wrong, I love the block count this weekend, and I love this pool, but if theres a possible issue, I think it's only fair to investigate to see what actually happened.

[Darthswan]

So I see I wasn't the only one.  I was going to bring this up when I got home.  My portion was cut in half also.

[necro_nemesis]

Same here but it's been a good run thereafter.

[retrojka]

yes i have had 2 very low points payouts today blocks 22106 and 22105.....both 50%
oh what i normally get......hopefully slush will correct this error....lol 

Same here, 50% of normal payout for 22106

my 200% more payout for 22106

in other block is normal payout

sounds like you got the jackpot!

normal payout is 0.00703204, in block 22106  first  0.02003204 down to payout 0.01350420

Why did my reward from block 22106 go from .04 to .01 just now

[mstrongbow]

yes i have had 2 very low points payouts today blocks 22106 and 22105.....both 50%
oh what i normally get......hopefully slush will correct this error....lol 

Same here, 50% of normal payout for 22106

my 200% more payout for 22106

in other block is normal payout

sounds like you got the jackpot!

normal payout is 0.00703204, in block 22106  first  0.02003204 down to payout 0.01350420

Why did my reward from block 22106 go from .04 to .01 just now

heh, mine went back up to my avg. payout amount

[retrojka]

yes i have had 2 very low points payouts today blocks 22106 and 22105.....both 50%
oh what i normally get......hopefully slush will correct this error....lol 

Same here, 50% of normal payout for 22106

my 200% more payout for 22106

in other block is normal payout

sounds like you got the jackpot!

normal payout is 0.00703204, in block 22106  first  0.02003204 down to payout 0.01350420

Why did my reward from block 22106 go from .04 to .01 just now

heh, mine went back up to my avg. payout amount

I knew my .04 payout was too good to be true

[kabopar]

My reward was also "cut in half".  
I raised a ticket, and things will be sorted out as usual.

Yep 22106 was also half here..   email sent to support:)

Regards

M

My payout was lower by 18% relatively to the proportional number of my shares.  A possible explanation to this is a sudden rise in the pool hash rate towards the end of the block, which decreases the payout of all the other miners (but at the same time make a significant contribution to solving that block faster).  Let's try to illustrate this with an example:  
The pool hash rate= 1800000 GH/s  Your hash rate=200 GH/s your expected reward=0.002777778 BTC
Now assume that Miner X joined the pool with 200000  GH/s a few minutes before the end of the block, due to Slush's 'anti-hopping' algorithm, Miner X's contribution receives almost full 'weight' despite occuring towards the end of the block, so the increased short-term hash rate at the end of the block is now 2000000  GH/s, your reward drops by 10% to 0.0025 BTC.  This is not due to any 'fault' at Slush.  Actually it might have been caused by a technical or other problem on one of the competing pools, which caused briefly a massive shift of miners to Slush as their 'backup pool'.
Just my 2 mbtc.
Enjoy the recent burst of solved blocks, which more than compensates for that 'disaster'...

Cheers

My understanding was that the calc, assuming you are mining at the time the block is found (you havent had a blip in providing hash rate etc) is  my shares / pool shares * Block Value..  for a rough calc.  (not deducting fees here)

therefore for block 22106  :-

22106  2014-05-19 16:30:41  11:23:16  18010425802  3586935   0.00206705  301575  25.10258983  97 confirmations left

which makes the calc 0.0049994

The three previous blocks using the same calc would have been :-  

22105 I get  0.0048193
22104 I get  0.0049920
22103 I get  0.0049467

All very similar and in fact almost identical to what was paid out, as were the 4 blocks post 22106

Whilst I appreciate your point about another pool jumpin in, to halve the rate paid it would have had to be approx 1872607.589 Ghash/s jumping in..  approx the rate when the block was found I believe, to drop it 50% and the your shares / total shares dont give those values, and we have also had reports of people getting double payout on that block, so something is not quite right.

This has been happening a lot since we moved to 60 minute averages, in fact one block, for me, dropped from .0048 as the calc to 0.0009 as the reward.

Whilst I appreciate your suggestion, I think something more drastic happened in this case and may be symptomatic of other blocks like this in the recent past.

I know it's not a huge issue, but when you only make 0.1 BTC a week (on average), it's a bigger deal

Regards

M

PS  dont get me wrong, I love the block count this weekend, and I love this pool, but if theres a possible issue, I think it's only fair to investigate to see what actually happened.

Apologies, my theory was sound, however in this case Slush made compensation adjustments, and now my reward for 22106 is about 1% above my 'proportional share', which is within the common variance.
I hope that your reward got fixed as well.

Cheers