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

[[Tycho]]

I got another question about CFD.  I read your site, but it doesn't say what the vertical lines represent on the CFD graph.  Could you kindly explain this to me.  Why does it take so long to hit 100%, and what math would you do to calculate what 100% is?

You can't hit 100% becuase there is always a chance that you won't find such hash at all (with a specific transaction pack and other variables that are changing constantly, so you don't need to fear this :).
So you can calculate for 99.999999...%, but not 100%

[1714149259]

1714149259

[1714149259]

1714149259

[1714149259]

1714149259

[Ian Maxwell]

So you can calculate for 99.999999...%, but not 100%

Just what we needed, an invitation to a 0.9999... vs 1 debate.  

[nster]

So you can calculate for 99.999999...%, but not 100%

Just what we needed, an invitation to a 0.9999... vs 1 debate.  

only 0.99999999999... with an infinite number of 9s = 1..... but this is a finished number we are talking about. 99.99999999999999999999999999999999999999999999999999999999999999999999 is not = to 100, however if we are talking about an infinitely precise number, (ie: infinite number of 9s after the decimal, only then is it = 1 to

in this case it would be 100^- not 100. It is entirely possible, though not very likely, that someone who mines at a difficulty of 1, with 100 Thash, doesn't find a block in a hundred years. I'd hate to be that guy though lol

[slush]

More *** from nster the troll
Ignore the troll and his turds

Hey, bobR, please ignore nster. We all know that he is the biggest troll here so it's not so important to remind that again and again. Thanks.

[Meni Rosenfeld]

I got another question about CFD.  I read your site, but it doesn't say what the vertical lines represent on the CFD graph.  Could you kindly explain this to me.  Why does it take so long to hit 100%, and what math would you do to calculate what 100% is?

As others mentioned, it takes infinitely long to hit 100%. For a general probability x, the number of shares is -ln(1-x)*difficulty.

[homer]

Vertical axis is percentage.

"For example, the theoretical curve shows that 87% of blocks should be found after less that (2 * the current difficulty) shares."

Oops.  What I meant to ask was about the Horizontal axis, not vertical.  My mistake.
How are the numbers 2,4,6,8,etc determined.  I understand the percentage (vertical) line, but I don't understand where the horizontal axis numbers come from.

Thanks for dealing with my noob'ness.

[Meni Rosenfeld]

Vertical axis is percentage.

"For example, the theoretical curve shows that 87% of blocks should be found after less that (2 * the current difficulty) shares."

Oops.  What I meant to ask was about the Horizontal axis, not vertical.  My mistake.
How are the numbers 2,4,6,8,etc determined.  I understand the percentage (vertical) line, but I don't understand where the horizontal axis numbers come from.

Thanks for dealing with my noob'ness.

The horizontal axis is multiples of the difficulty. So point 2 on this axis represents a number of shares equal to twice the difficulty. The corresponding point on the vertical axis, 87%, means that 87% of all rounds will end before reaching this number of shares.

[TenthReality]

Slush,

What kind of bribery will it take to get the average daily reward graph in tabular form, or even JSON, additionally any shot at getting an "average reward per worker" graph of some kind? 

[ishav]

Slush,

What kind of bribery will it take to get the average daily reward graph in tabular form, or even JSON, additionally any shot at getting an "average reward per worker" graph of some kind? 

Since the graphs are generated by Javascript you could grab the data and make a tabular form from the html. It on line 160, the reward_time_data variabel.

[mrjones]

Is there any way to see which blocks a particular worker found? I noticed that one of mine found one today and purely out of curiosity I'm wondering which block it was. I'd take a certain amount of pride in being able to say, "Oh, yeah, block 117551, that was me!"

[homer]

Is there any way to see which blocks a particular worker found? I noticed that one of mine found one today and purely out of curiosity I'm wondering which block it was. I'd take a certain amount of pride in being able to say, "Oh, yeah, block 117551, that was me!"

I noticed that also.  It doesn't seem like mining.bitcoin.cz or deepbit.net have very detailed stats for their users, and everything is delayed which makes it impossible for me to watch my stats in realtime, and that sucks.  Is there anyway to get my stats in a non-delayed form?

[homer]

Oops.  What I meant to ask was about the Horizontal axis, not vertical.  My mistake.
How are the numbers 2,4,6,8,etc determined.  I understand the percentage (vertical) line, but I don't understand where the horizontal axis numbers come from.

Thanks for dealing with my noob'ness.

The horizontal axis is multiples of the difficulty. So point 2 on this axis represents a number of shares equal to twice the difficulty. The corresponding point on the vertical axis, 87%, means that 87% of all rounds will end before reaching this number of shares.

That makes more sense. Thank you for explaining that.

[zoro]

Is there any way to see which blocks a particular worker found? I noticed that one of mine found one today and purely out of curiosity I'm wondering which block it was. I'd take a certain amount of pride in being able to say, "Oh, yeah, block 117551, that was me!"

I noticed that also.  It doesn't seem like mining.bitcoin.cz or deepbit.net have very detailed stats for their users, and everything is delayed which makes it impossible for me to watch my stats in realtime, and that sucks.  Is there anyway to get my stats in a non-delayed form?

well,
mining.bitcoin.cz has real time statistics of shares and found blocks but they are displayed as unconfirmed!
deepbit has the one hour delay since at that time the confirmation is over

[slush]

What kind of bribery will it take to get the average daily reward graph in tabular form, or even JSON,

Temporary you can use json-encoded data in graphs page. There will be direct json interface for stats like this in next release.

additionally any shot at getting an "average reward per worker" graph of some kind? 

That's quite hard to do. Everything (mainly reward calculations) is bounded to user account, so per-worker stats are not possible at the moment.

[slush]

Is there any way to see which blocks a particular worker found? I noticed that one of mine found one today and purely out of curiosity I'm wondering which block it was. I'd take a certain amount of pride in being able to say, "Oh, yeah, block 117551, that was me!"

Planning this into next release.

[mrjones]

Planning this into next release.

Nice!  Also, I forgot to say thanks for looking into the weirdness in pool block 2861 (i.e. block 116884) and taking care of it and distributing the earnings appropriately.  Greatly appreciate your responsiveness!

[slurch]

Am I the only lucky noob who's not getting payouts? Granted, I suck, and my miners suck, but I've been over threshold for like 5 hours. How often do payouts happen, anyway?

Edit: Just came through...I guess I just need to learn how to wait.

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

[slurch]

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?

I am guessing (and I'm almost certainly wrong, here, owing to my noobiness) that only the lucky share finders for this block got paid...according to what you posted, the solution was discovered after a mere 55 shares. Only the workers who found those shares are getting a payout for this block.

[Miner-TE]

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