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

[aurel57]

How about block 18995? Anyone have issues with payout? My statistics say "none" shares submitted so no reward as well, which is difficult to believe since I run 24/7 with my ASICS. Hopefully Slush is already on top of it.

my problem is with #18994 :

18995 2013-07-07 16:13:53 0:03:48   1004576       310 0.00741798   245313  25.08610005 87 confirmations left 
18994 2013-07-07 16:10:05 2:30:19   43504966  11560 0.00444670    245312  25.24340000 86 confirmations left 
18993 2013-07-07 13:39:46 1:16:36   21972047    5907 0.00685585   245292  25.31574798 66 confirmations left 

I was hoping it was going to be corrected before it got confirmed but I guess by the low amount of others having problems with 18994 it must have been on my end?

[1550379394]

1550379394

[macsheadroom]

How about block 18995? Anyone have issues with payout? My statistics say "none" shares submitted so no reward as well, which is difficult to believe since I run 24/7 with my ASICS. Hopefully Slush is already on top of it.

my problem is with #18994 :

18995 2013-07-07 16:13:53 0:03:48   1004576       310 0.00741798   245313  25.08610005 87 confirmations left  
18994 2013-07-07 16:10:05 2:30:19   43504966  11560 0.00444670   245312  25.24340000 86 confirmations left  
18993 2013-07-07 13:39:46 1:16:36   21972047    5907 0.00685585   245292  25.31574798 66 confirmations left  

I was hoping it was going to be corrected before it got confirmed but I guess by the low amount of others having problems with 18994 it must have been on my end?

I was also about halved, 18995 is ever so slightly above "normal" for my 3 Gh
18995    2013-07-07 16:13:53    0:03:48    1004576    171    0.00433259    245313    25.08610005    20 confirmations left
18994    2013-07-07 16:10:05    2:30:19    43504966    6332    0.00237623    245312    25.24340000    19 confirmations left
18993    2013-07-07 13:39:46    1:16:36    21972047    3218    0.00372723    245292    25.31574798    confirmed

[gourmet]

Question: Suggested difficulty option box.
What is the point in this box? It optional but then if its optional dose it really matter? I'm running just 4 Block Erupters on Slush's Pool should I change my setting and if so to what?  

 For those with large amount of hash power, setting a higher difficulty will reduce the network bandwidth consumed by submitted shares.  You don't have enough hashpower for it to matter.   I wouldn't worry about it.  

So just curious at what point would you need to set a higher difficulty? How many Mhash/s are we talkin'? I know what the website suggests according to Mhash/s but is this realistic? What have others experienced?

When you set a value there, it tells the servers "Don't send me anything less than this."  The maximum is whatever diff the server decides to send.  For example, one of my miners is set for diff 2 -- most shares I get are between 2-1000, but I often get shares as high as 10M to work.

Not really.
The difficulty value you set in your client tells your client to send only shares of that difficulty (and higher) to the server. And it tells the server that you will be doing so.
The server will than count each your difficulty 2 (or higher) share as two difficulty 1 shares (when you set the difficulty to 2, of course). Your network traffic is then lower, and lower is also your demand on the server capacity.

The server makes no decision about what difficulty it sends you. It in fact can't do anything like that. You don't get shares as high as 10M to work. You don't get any shares to work on from the server.

The server gives you some data to work on, and it's a matter of your fortune to find a share. When your client is set to send shares of diff 1, it sends all shares it finds to the server. To find one such basic share you have to compute 2³² hashes at average.

When you set the difficulty to a higher number, only shares of that difficulty (and higher, of course) are sent to the server. This is useful when your share rate would be too (unnecesarily) high with shares of diff 1.

[nottm28]

245443 is not ours

[5120-01-518-6126]

Question: Suggested difficulty option box.
What is the point in this box? It optional but then if its optional dose it really matter? I'm running just 4 Block Erupters on Slush's Pool should I change my setting and if so to what?  

 For those with large amount of hash power, setting a higher difficulty will reduce the network bandwidth consumed by submitted shares.  You don't have enough hashpower for it to matter.   I wouldn't worry about it.  

So just curious at what point would you need to set a higher difficulty? How many Mhash/s are we talkin'? I know what the website suggests according to Mhash/s but is this realistic? What have others experienced?

When you set a value there, it tells the servers "Don't send me anything less than this."  The maximum is whatever diff the server decides to send.  For example, one of my miners is set for diff 2 -- most shares I get are between 2-1000, but I often get shares as high as 10M to work.

Not really.
The difficulty value you set in your client tells your client to send only shares of that difficulty (and higher) to the server. And it tells the server that you will be doing so.
The server will than count each your difficulty 2 (or higher) share as two difficulty 1 shares (when you set the difficulty to 2, of course). Your network traffic is then lower, and lower is also your demand on the server capacity.

The server makes no decision about what difficulty it sends you. It in fact can't do anything like that. You don't get shares as high as 10M to work. You don't get any shares to work on from the server.

The server gives you some data to work on, and it's a matter of your fortune to find a share. When your client is set to send shares of diff 1, it sends all shares it finds to the server. To find one such basic share you have to compute 2³² hashes at average.

When you set the difficulty to a higher number, only shares of that difficulty (and higher, of course) are sent to the server. This is useful when your share rate would be too (unnecesarily) high with shares of diff 1.

Thanks for the clarification 

[bspurloc]

How about block 18995? Anyone have issues with payout? My statistics say "none" shares submitted so no reward as well, which is difficult to believe since I run 24/7 with my ASICS. Hopefully Slush is already on top of it.

my problem is with #18994 :

18995 2013-07-07 16:13:53 0:03:48   1004576       310 0.00741798   245313  25.08610005 87 confirmations left 
18994 2013-07-07 16:10:05 2:30:19   43504966  11560 0.00444670    245312  25.24340000 86 confirmations left 
18993 2013-07-07 13:39:46 1:16:36   21972047    5907 0.00685585   245292  25.31574798 66 confirmations left 

I was hoping it was going to be corrected before it got confirmed but I guess by the low amount of others having problems with 18994 it must have been on my end?

Mine was wrong too, oh well.

[aurel57]

Today is a day why most are here on Slush's Pool... 30 blocks found in the last 24 hours.. ( I guess its only 29 as we did have the 1 invalid today)

[TObject]

Question: Suggested difficulty option box.
What is the point in this box? It optional but then if its optional dose it really matter? I'm running just 4 Block Erupters on Slush's Pool should I change my setting and if so to what?  

 For those with large amount of hash power, setting a higher difficulty will reduce the network bandwidth consumed by submitted shares.  You don't have enough hashpower for it to matter.   I wouldn't worry about it.  

So just curious at what point would you need to set a higher difficulty? How many Mhash/s are we talkin'? I know what the website suggests according to Mhash/s but is this realistic? What have others experienced?

When you set a value there, it tells the servers "Don't send me anything less than this."  The maximum is whatever diff the server decides to send.  For example, one of my miners is set for diff 2 -- most shares I get are between 2-1000, but I often get shares as high as 10M to work.

Not really.
The difficulty value you set in your client tells your client to send only shares of that difficulty (and higher) to the server. And it tells the server that you will be doing so.
The server will than count each your difficulty 2 (or higher) share as two difficulty 1 shares (when you set the difficulty to 2, of course). Your network traffic is then lower, and lower is also your demand on the server capacity.

The server makes no decision about what difficulty it sends you. It in fact can't do anything like that. You don't get shares as high as 10M to work. You don't get any shares to work on from the server.

The server gives you some data to work on, and it's a matter of your fortune to find a share. When your client is set to send shares of diff 1, it sends all shares it finds to the server. To find one such basic share you have to compute 2³² hashes at average.

When you set the difficulty to a higher number, only shares of that difficulty (and higher, of course) are sent to the server. This is useful when your share rate would be too (unnecesarily) high with shares of diff 1.

There are about 30 seconds between a miner connects and starts hashing and the suggested difficulty is set. If a share is submitted within these 30 seconds at what difficulty will it be counted: one, suggested difficulty, actual difficulty, something else?

[gourmet]

Question: Suggested difficulty option box.
What is the point in this box? It optional but then if its optional dose it really matter? I'm running just 4 Block Erupters on Slush's Pool should I change my setting and if so to what?  

 For those with large amount of hash power, setting a higher difficulty will reduce the network bandwidth consumed by submitted shares.  You don't have enough hashpower for it to matter.   I wouldn't worry about it.  

So just curious at what point would you need to set a higher difficulty? How many Mhash/s are we talkin'? I know what the website suggests according to Mhash/s but is this realistic? What have others experienced?

When you set a value there, it tells the servers "Don't send me anything less than this."  The maximum is whatever diff the server decides to send.  For example, one of my miners is set for diff 2 -- most shares I get are between 2-1000, but I often get shares as high as 10M to work.

Not really.
The difficulty value you set in your client tells your client to send only shares of that difficulty (and higher) to the server. And it tells the server that you will be doing so.
The server will than count each your difficulty 2 (or higher) share as two difficulty 1 shares (when you set the difficulty to 2, of course). Your network traffic is then lower, and lower is also your demand on the server capacity.

The server makes no decision about what difficulty it sends you. It in fact can't do anything like that. You don't get shares as high as 10M to work. You don't get any shares to work on from the server.

The server gives you some data to work on, and it's a matter of your fortune to find a share. When your client is set to send shares of diff 1, it sends all shares it finds to the server. To find one such basic share you have to compute 2³² hashes at average.

When you set the difficulty to a higher number, only shares of that difficulty (and higher, of course) are sent to the server. This is useful when your share rate would be too (unnecesarily) high with shares of diff 1.

There are about 30 seconds between a miner connects and starts hashing and the suggested difficulty is set. If a share is submitted within these 30 seconds at what difficulty will it be counted: one, suggested difficulty, actual difficulty, something else?

Well, the situation with the share difficulty is a bit more complicated than I've written so far. There are some pools that set the target (minimum difficulty) for the shares obtained from the client. I've not mentioned them since this thread is about Slush's pool.
You can find those pools in the list Comparison of mining pools at the bitcoin wiki marked as Dynamic in the Variance column.
Once again, this does not apply to Slush's pool.

So, those pools can set different target (minimum difficulty) for the shares accepted from the clients. As your information about the 30 seconds' interval must have come from some of those pools, one could quite well recommend you to look for the answer to your question at the same place.

I could imagine that the client sends shares of diff 1 for some initial time interval in the round (30 seconds mentioned by you), and the server measures (roughly) client's hashrate this way. It (the server) then makes a decision based on this finding, what share difficulty target would be optimal for this particular client. (But this is only my speculation.) This method would have one more advantage of using finer resolution for extra short rounds, where the higher target would cause too a high variance.
[edit]If this "calibration" occurs only after client connection and not in each round, this advantage does not apply, thouhg.[/edit]

Some pools also set the target for shares to a fixed value higher than one. Those pools, however, need no time interval to do so.

[tiktoc]

The pool software that slush wrote does a variable diff check every 30 seconds . Assume his pool would do something similar.

[gourmet]

The pool software that slush wrote does a variable diff check every 30 seconds . Assume his pool would do something similar.

What does does a variable diff check mean?
How is that related to the previous discussion / to my last post?
Can you post a link that confirmes/explains what you've written?

[tiktoc]

It does what you mentioned in the last section of your second to last post.

https://github.com/generalfault/stratum-mining/blob/master/conf/config_sample.py

scroll down to the Pool Difficulty Settings

It actually checks every 300 secs to see if the miner is doing at least one share per a 30 seconds. Was on a phone before when I posted, so sorry for not meeting the aggressive citation and link checking for your needs.

[EasyQuest]

Now all the computers are litecoin mining exempt one which is dual mining with litecoin and bitcoin at the same time with one cgminer software

Another issue which has arises is one 7970 is only mining at 557 KH/s every other card is hashing higher, I am currently setting up a bios flash to get the PowerColor to the GHz edition to see what happen. Wish me luck.

[Trongersoll]

Now all the computers are litecoin mining exempt one which is dual mining with litecoin and bitcoin at the same time with one cgminer software

Another issue which has arises is one 7970 is only mining at 557 KH/s every other card is hashing higher, I am currently setting up a bios flash to get the PowerColor to the GHz edition to see what happen. Wish me luck.

What does this have to do with Slush Pool?

[EasyQuest]

Now all the computers are litecoin mining exempt one which is dual mining with litecoin and bitcoin at the same time with one cgminer software

Another issue which has arises is one 7970 is only mining at 557 KH/s every other card is hashing higher, I am currently setting up a bios flash to get the PowerColor to the GHz edition to see what happen. Wish me luck.

What does this have to do with Slush Pool?

Nothing But I still mine on slush

[r.padgett]

Now all the computers are litecoin mining exempt one which is dual mining with litecoin and bitcoin at the same time with one cgminer software

Another issue which has arises is one 7970 is only mining at 557 KH/s every other card is hashing higher, I am currently setting up a bios flash to get the PowerColor to the GHz edition to see what happen. Wish me luck.

Let me know how this turns out. I have the GHz edition and can't get any faster than that.

[crazyates]

Now all the computers are litecoin mining exempt one which is dual mining with litecoin and bitcoin at the same time with one cgminer software

Another issue which has arises is one 7970 is only mining at 557 KH/s every other card is hashing higher, I am currently setting up a bios flash to get the PowerColor to the GHz edition to see what happen. Wish me luck.

Let me know how this turns out. I have the GHz edition and can't get any faster than that.

Ckolivas said it's a known issue with GHz cards. I can't get my Gigabyte GHz card past 550KH either. If you want to LTC mine, you gotta buy a ref 7970.

[EasyQuest]

Now all the computers are litecoin mining exempt one which is dual mining with litecoin and bitcoin at the same time with one cgminer software

Another issue which has arises is one 7970 is only mining at 557 KH/s every other card is hashing higher, I am currently setting up a bios flash to get the PowerColor to the GHz edition to see what happen. Wish me luck.

Let me know how this turns out. I have the GHz edition and can't get any faster than that.

Ckolivas said it's a known issue with GHz cards. I can't get my Gigabyte GHz card past 550KH either. If you want to LTC mine, you gotta buy a ref 7970.

Weird how my other 7970s of the same brand and model mine more than this card and I did nothing to the cards. One of the 7970 Powercolor V3 is doing 735 KH/s!!

I have not check the bios on all the 7970 and I am not at home to do the BIOS flash, so it will be a little later tonight.

Also none are GHz Edition all are standard clocks and all.

[bspurloc]

Diff going up tomorrow!

10/07/2013  21:51      26'405'169.95

[Trongersoll]

Diff going up tomorrow!

10/07/2013  21:51      26'405'169.95

Oh joy.