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

[allinvain]

And that whole round only lasted 6 sec.  I was also unlucky.

Ah I see. That makes sense. But I still had 55 shares in according to the stats, so 

[1713582748]

1713582748

[1713582748]

1713582748

[1713582748]

1713582748

[1713582748]

1713582748

[slurch]

And that whole round only lasted 6 sec.  I was also unlucky.

Ah I see. That makes sense. But I still had 55 shares in according to the stats, so  

There were only 55 shares for that block, until it was solved -- that's what it took everyone. Since the whole block was only 6 seconds, you probably wouldn't have even seen it during the processing if you had found one. You would have gotten a huge reward, though.

Edit: My report for this block looks exactly the same as yours.

[allinvain]

And that whole round only lasted 6 sec.  I was also unlucky.

Ah I see. That makes sense. But I still had 55 shares in according to the stats, so  

There were only 55 shares for that block, until it was solved -- that's what it took everyone. Since the whole block was only 6 seconds, you probably wouldn't have even seen it during the processing if you had found one. You would have gotten a huge reward, though.

Edit: My report for this block looks exactly the same as yours.

OK, I see. Well I am satisfied with that answer. As long as it wasn't "just me"...

On to other blocks!

[slush]

Code:

3073	2011-04-10 13:06:20	0:00:06	55	none	117657	 21 confirmations left

Any reason why for the reward column is says "none" even though I participated in that round? This is block 117657. What happened there?

"Total shares" is commonly misunderstood. That's number of all shares of whole pool, not user's shares. So 49BTC was divided between those miners who submitted at least one share from those 55 total.

[allinvain]

Code:

3073	2011-04-10 13:06:20	0:00:06	55	none	117657	 21 confirmations left

Any reason why for the reward column is says "none" even though I participated in that round? This is block 117657. What happened there?

"Total shares" is commonly misunderstood. That's number of all shares of whole pool, not user's shares. So 49BTC was divided between those miners who submitted at least one share from those 55 total.

Ahhh..gotcha...I was under the impression all this time that those represented only my shares not the whole pool. Thanks for clearing that up.

Those miners sure caught a lucky break and a huge payday! Sucks for those with a slower hash rate though. Or maybe the hash rate didn't matter just an issue of who (due to luck of the draw) managed to put in some shares before the round was over?

[slush]

Those miners sure caught a lucky break and a huge payday! Sucks for those with a slower hash rate though. Or maybe the hash rate didn't matter just an issue of who (due to luck of the draw) managed to put in some shares before the round was over?

Pool contribution is still 'fair', even in fast rounds. I mean - everybody have same chance to hit one of 55 shares, proportionally to their hashrate. With 100mhash/s, you have only 100x higher chance to hit one share than 1mhash/s user. So fast round does not add any advantage to fast miners...

Highest user reward for block 117657 was 2.67 BTC for 3 shares, so rewards were still distributed pretty nicely (nobody hit, for example 20 BTC for himself).

[allinvain]

Those miners sure caught a lucky break and a huge payday! Sucks for those with a slower hash rate though. Or maybe the hash rate didn't matter just an issue of who (due to luck of the draw) managed to put in some shares before the round was over?

Pool contribution is still 'fair', even in fast rounds. I mean - everybody have same chance to hit one of 55 shares, proportionally to their hashrate. With 100mhash/s, you have only 100x higher chance to hit one share than 1mhash/s user. So fast round does not add any advantage to fast miners...

Highest user reward for block 117657 was 2.67 BTC for 3 shares, so rewards were still distributed pretty nicely (nobody hit, for example 20 BTC for himself).

Thanks for the further clarification slush. Keep up the good work! So far I'm very happy with the way you're running your pool.

Cheers!

[slush]

Damn, bitcoind crashed on deadlock during sending rewards, again. There are many pending payouts but nothing lost; I'll solve the issue in few hours.

[diven]

Any chance of adding a "Your Shares" column to the block history table on the statistics page?

[Dobrodav]

I`m not give a fk to speculations,  I`m just run on different pools (as novice) for 48 hours and observe the outcome.  Now i`m done with deepbit and turn to slush pool to observe 24-hrs bitcoin outcome. 48 hours is definetly not anough  for some stastic conclusion, but i`m think that is only way to get your own point of view. If there will be some significall difference i`m will post again. But i`m want to point at general idea - try it by yorself, and then make conclusions.

[Qrr]

I'm not getting my payment, I have my threshold @ 6.0 and I have 6.22 confirmed BTC 

[nster]

I`m not give a fk to speculations,  I`m just run on different pools (as novice) for 48 hours and observe the outcome.  Now i`m done with deepbit and turn to slush pool to observe 24-hrs bitcoin outcome. 48 hours is definetly not anough  for some stastic conclusion, but i`m think that is only way to get your own point of view. If there will be some significall difference i`m will post again. But i`m want to point at general idea - try it by yorself, and then make conclusions.

such small time span for such similar payout pools means NOTHING. It would only measure the luck factor for rthose 24 hours of each pool

[slush]

I'm not getting my payment, I have my threshold @ 6.0 and I have 6.22 confirmed BTC 

I was probably unclear in my previous post, because few people wrote me PMs about this, too. Because of troubles with bitcoind I had to temporary stop payouts. I'm working on that right now, will be fixed in hour or two.

[dansthunder]

How goes the fixing Slush?

[slush]

I just sent all payments. It took little more time because I wrote script which automatize the task for the future.

There is bitcoind patch available for the bitcoind deadlocks and I hope that the issue will be solved permanently in the near future. But I don't fully understand patched stuff, so I'm waiting to it's peer review by someone else than patch author. It isn't fun to test patches on such large payments .

[slurch]

Highest user reward for block 117657 was 2.67 BTC for 3 shares, so rewards were still distributed pretty nicely (nobody hit, for example 20 BTC for himself).

That's still pretty epic for what...6 seconds of work?

[allinvain]

Highest user reward for block 117657 was 2.67 BTC for 3 shares, so rewards were still distributed pretty nicely (nobody hit, for example 20 BTC for himself).

That's still pretty epic for what...6 seconds of work?

This is the bitcoin equivalent of winning the lottery!

[Enky1974]

Is it possible to empty the account? i've 0.75 btc and i'm not mining at the moment, due to this i'll never cross any thresold and i'll never receive any payments:) maybe add a button to empy the confirmed reward.
I tried to set the thresold to 0.50 but doesnt work.
Thanks

[slush]

I tried to set the thresold to 0.50 but doesnt work.

What kind of trouble you got? You can set threshold to 0.01 and system will send almost everything to you (rewards under 0.01 will remain on account, because Bitcoin client cannot handle sub-cent  amounts properly yet).

[Enky1974]

I tried to set the thresold to 0.50 but doesnt work.

What kind of trouble you got? You can set threshold to 0.01 and system will send almost everything to you (rewards under 0.01 will remain on account, because Bitcoin client cannot handle sub-cent  amounts properly yet).

sorry Slush it worked, i received the amount now, thanks.