Topic: [4+ EH] Slush Pool (slushpool.com); Overt AsicBoost; World First Mining Pool - page 743. (Read 4382801 times)

command line:  cgminer --no-submit-stale

or cgminer.conf:

"no-submit-stale" : true,

Is 0.00000058 BTC for 840 shares right? Seems very low to me.

Is remember seeing not send stale share setting in miner?  Know where is in what?
Thank you.

My workers are only 220Mh/s (I have 32 of them).  The problem isn't the hardware, it's the system design.  The miner needs to support long polling, then immediately flush all current work and start on the new job.  If you can do this quick enough you'll get those early shares.  The hash rate will affect the number of shares you get (these blocks are below average for me, so someone else is faster) but you will get something.

It isn't as easy as that. If you mine on a start of a 4 or 8 hour block and stop after 2 hours you will defenetly get nothing. If you finish close to the end you will get about full reword. So it is important when you stop mining. But since you can't know when a block will finish it is hard to use this in your advantage. So look at statistic page and find when you have mine this 2 hours.

Fair enough.

Here are my "stats" on the blocks you reported with missing shares.  You haven't given enough detail to make a conclusive argument that you're missing anything.

18034 2013-05-14 19:27:14 3:35:30 30026262 7487 0.00596651 none 236202  25.10024000 confirmed  
18033 2013-05-14 15:51:44 3:34:13 29829536 7495 0.00591263 none 236182  25.43437400 confirmed  
18032 2013-05-14 12:17:31 1:26:37 12093844 2903 0.00677666 none 236165  25.15775000 confirmed  
18031 2013-05-14 10:50:54 0:01:10 157750 46 0.00721302 none 236154  25.06650000 confirmed  
18030 2013-05-14 10:49:44 0:27:05 3751992 968 0.00663882 none 236153  25.18090000 confirmed  
18029 2013-05-14 10:22:39 1:18:11 10929435 2605 0.00623198 none 236148  25.61227001 confirmed  
18028 2013-05-14 09:04:28 1:04:00 8890231 2174 0.00567510 none 236145  25.34600000 confirmed  
18027 2013-05-14 08:00:28 0:33:49 4716423 1128 0.00582061 none 236136  25.16020001 confirmed


I still stand behind my position that Slush and his pool is worth some amount of loyalty.  If you feel you were shorted on a couple blocks, likely because of a programming error, and leave, then so be it.... but hasty decisions like that often lead to nowhere.

I'm just trying to encourage the rest of you who haven't left, but feel like "something is wrong" to just relax for a bit and wait for Slush to return.  That's it.  And to stop with the FUD.

If you mine in an 4 or 8 hour block you don't get reward?

Look at statistics. If you were not looking you might mine in a 4 or 8 hours block. If this is a case you just had bed luck but this is the way it is with Slush method.

There is a HUGE problem with nodes not reporting shares, among other things. Just read the last ~500 posts. And block #236442 which is the last one "found" belongs to BTC Guild. If some of you haven't experienced any problems, fine. Sooner or later you will.

Slush's absence is very unfortunate and I won't return to my old favorite pool until he has confirmed all problems are sorted.

I also seem to have problems with slush's pool. Yesterday my total reward was about 0.0099 BTC and I let it mine for two hours or so. But this morning the reward is still the same. I kinda feel like something doesn't work correctly.

hmm... I don't find Lucko posting crap, you on the other hand definitely...

Same here the previous night - my fastest miner was not counted though it seemed to be working correctly (/shrug cannot tell for sure I was sleeping but again if my miner stops it doesn't recover on its own and in the morning it looked fine)

18034    2013-05-14 19:27:14    3:35:30    30026262    2702    0.00259934    236202    25.10024000    confirmed <-- Normal, usual fluctuations
18033    2013-05-14 15:51:44    3:34:13    29829536    2654    0.00208799    236182    25.43437400    confirmed <-- Normal, usual fluctuations
18032    2013-05-14 12:17:31    1:26:37    12093844    387    0.00162982    236165    25.15775000    confirmed  <-- Recovering ??
...
All those below are missing shares from a faster miner
18031    2013-05-14 10:50:54    0:01:10    157750    3    0.00041860    236154    25.06650000    confirmed
18030    2013-05-14 10:49:44    0:27:05    3751992    110    0.00081932    236153    25.18090000    confirmed
18029    2013-05-14 10:22:39    1:18:11    10929435    317    0.00102232    236148    25.61227001    confirmed
18028    2013-05-14 09:04:28    1:04:00    8890231    227    0.00062620    236145    25.34600000    confirmed
18027    2013-05-14 08:00:28    0:33:49    4716423    114    0.00064109    236136    25.16020001    confirmed


Just posting since somebody else noted the same. Also I definitely see shares missing from one of the miners on the round but normally just on 1 block not the series of blocks in the row.
18026    2013-05-14 07:26:39    0:18:31    2610383    60    0.00060960

I've noticed a problem that has occurred twice over the past week or so. I run two GPU miners (with GUIMiner) at approximately 160Mh/s each. Now GUIMiner reports accepted shares, accepted shares for the last hour and network connection problems in its log. These are the only indicators of miner health directly available to me and are not evidence of anything.

What I have seen is that my miners report normal activity with no connection problems and yet one of the miners has no accepted shares reported on my account log on Slush's pool. The first occasion showed over six hours since the last share had been accepted; the second occasion showed over nine minutes without a share accepted.  On both occasions, the time since the last share accepted matched the time since a block was found on Slush's pool but not necessarily the last block.  It appears as if one of my miner's shares were no longer be credited after the pool's 'block found' event processing.

On both occasions, I stopped and restarted GUIMiner for the affected miner and share accepted activity on my pool account log resumed normally. The shares lost were not recovered.

On one other occasion, I saw that all shares from both miners were reported on my account log as if they had all come from one of my miners with the other showing no accepted shares.  As best as I could determine, this also was related to 'block found' processing on the pool.  That is, after finding a block, Slush's pool merged all accepted shares from both miners into one of the miner's accounts.

I hope this information might prove useful to Slush.

If you are getting any more full of yourself your head will be exploding.  Is donkey rears like you causing me to moving elsewhere to get away from.  Slush must appreciating junior member who becomes himself boss of whole pool and makes users run away.

Edit - OK is good.  Is press USER IS IGNORED button is making forum much better.  Sorry for my angry.

never mind.... this lucko isn't worth responding to.  get some logs when you engage your "backup to the backup" pool and come back and bitch with some real facts.  Until then, move the luck on and stop posting nonsense.

I guess this is good-bye and good-riddance then!!! 

With more and more ASICs coming, much bigger load is expected to the pools, so maybe they are working on some optimizations?

Having seen how Slush operates, he would normally post something even if it were 'I will look into any issues when I get a moment' kind of post, even when up to his ears in shit when the OVH hack happened and he was working flat out to sort it he still maintained comms.
I hope all is well with him but am a wee bit concerned.

Yes but even saying I'm hire will look into next mount would help. He is away now for 15 days. As far as I know this is not normal for him and saying anything else is just lying to yourself. Something is wrong. Even on holidays(I don't believe that they are so long) I would post something like I will look into this when I will be back on... So relay there is something else and the only explanation I can think of is that something happen to him and can't post or look at the pool.