Since yesterday prize of the block is reduced by about 30%. Does anyone know why this is happening?
pool has gone up to 9612754 Gh in the last 12 hours
Topic: [4+ EH] Slush Pool (slushpool.com); Overt AsicBoost; World First Mining Pool - page 243. (Read 4382671 times)
September 12, 2014, 07:55:35 AM
pool has gone up to 9612754 Gh in the last 12 hours
September 12, 2014, 07:41:33 AM
Since yesterday prize of the block is reduced by about 30%. Does anyone know why this is happening?
http://i60.tinypic.com/68zh1c.jpg
http://i60.tinypic.com/68zh1c.jpg
September 12, 2014, 05:59:30 AM
Bet one of the big pools has an outage and miners have kicked in here as a second address. 
September 12, 2014, 05:46:48 AM
I fully aware of size of pool and effect on payout. But what I saw before I went to bed is completely different from what I see when I woke up.
September 12, 2014, 05:21:36 AM
I'm just throwing this out there...Pool size has increased almost 50%, so payouts have to be spread out to more users, which makes the payouts smaller. But I would imagine, with the huge increase in pools hashing, there would be the potential for more blocks per day, hopefully eating through them faster than before.
But my theory goes to poop with the current block taking over 8 hours now.
EDIT: Uhh, yeah, pretty much EXACTLY what he said!!
But my theory goes to poop with the current block taking over 8 hours now.
EDIT: Uhh, yeah, pretty much EXACTLY what he said!!
September 12, 2014, 05:18:44 AM
As pool rate went up by nearly 50%, my reward came down 33%. Upside should be more blocks? But latest one still over 8 hrs and counting. 
September 12, 2014, 05:04:54 AM
The last two blocks we found, my reward has been cut in half. Before I went to bed it was double what I currently see now. Any clue? Damn this pool size, also.
September 12, 2014, 01:52:33 AM
overreacting newbs gunna overreact
September 12, 2014, 12:33:55 AM
Yep I think we were all a bit stunned when the pool rate suddenly jumped from 66 to over 90. I reloaded page 3 times to make sure I wasn't seeing things 
September 12, 2014, 12:02:12 AM
hash power almost bet Eligius pool.
September 11, 2014, 11:42:49 PM
only sucking part is all the people from other pools that are asleep not realizing their stuff is pointing at slush!
need to shave off that extra hashing power!! ugh!! i dont have my new s3's yet to overcome such things!!
need to shave off that extra hashing power!! ugh!! i dont have my new s3's yet to overcome such things!!
September 11, 2014, 10:41:33 PM
It's been a bit since this has happened. Slush always takes care of it, just always very little or no comms. It can suck to see 40th/s not reporting. I figure if they don't fail over to a backup pool they'll end up getting reported correctly (2x expierence with this happening ). Like folks have said - the front end and the back end are different servers. Patience just sucks sometimes ;-) I still average higher payouts here over a year now.
Lip
Lip
Thanks for the heads up and yeah I've been mining with slush since early spring...just never saw he front-end fail like that in my short time here.
Glad everything is kosher and I did not need to change to a failover
September 11, 2014, 10:38:45 PM
It's been a bit since this has happened. Slush always takes care of it, just always very little or no comms. It can suck to see 40th/s not reporting. I figure if they don't fail over to a backup pool they'll end up getting reported correctly (2x expierence with this happening ). Like folks have said - the front end and the back end are different servers. Patience just sucks sometimes ;-) I still average higher payouts here over a year now.
Lip
Lip
Agreed
September 11, 2014, 10:37:29 PM
It's been a bit since this has happened. Slush always takes care of it, just always very little or no comms. It can suck to see 40th/s not reporting. I figure if they don't fail over to a backup pool they'll end up getting reported correctly (2x expierence with this happening ). Like folks have said - the front end and the back end are different servers. Patience just sucks sometimes ;-) I still average higher payouts here over a year now.
Lip
Lip
September 11, 2014, 10:10:32 PM
pool back to normal now.
September 11, 2014, 10:05:23 PM
Talk about pool size doubling. Ouch.
September 11, 2014, 09:18:44 PM
Same for me, but out of 6 miners, only connects 3 of 6 on the Account page even after rebooting all miners twice...
September 11, 2014, 09:14:52 PM
my account showed "Zero hash rate in the past 3 hrs & 34 mins" now. but all my miners are hashing and showed that their shares are accepted by Slush's Pool. on block # 320231 my reward is low and on block # 320241, i got "no" reward. now, block # 320249 is coming in and i'm pretty sure, my reward would still be "zero" again even though, all my miners are hashing fine and reporting accepted shares... oh boy... what a waste of time this situation brings me now... not good... really not good... tsk tsk tsk...
tried to reboot all miners a number of times this morning but to no avail... as of this writing, i'm stuck here in the office...
tried to reboot all miners a number of times this morning but to no avail... as of this writing, i'm stuck here in the office...
September 11, 2014, 08:49:03 PM
I'm showing that miners on Ghash.io are having the same problems. But Slushes so far are showing the worst out of anyone I checked with.
It may be the hubs where a lot of the traffic goes out or comes in to the USA. All it takes is one of those massive units to blow and
it can effect a lot of Internet activity. (Then again, maybe slush is pulling the plug out and saying....just kidding! Then plugging it back in!)
It may be the hubs where a lot of the traffic goes out or comes in to the USA. All it takes is one of those massive units to blow and
it can effect a lot of Internet activity. (Then again, maybe slush is pulling the plug out and saying....just kidding! Then plugging it back in!)
September 11, 2014, 08:29:22 PM
My 2 workers dropped off 5 and 15 minutes before the block ended according to my stats page.
I was messing around in there GUIs while this all happened and they were hashing and submitting all along.
I was messing around in there GUIs while this all happened and they were hashing and submitting all along.
Jump to: