Post
Topic
Board Pools
Re: [8500 GH/s] Slush's Pool (mining.bitcoin.cz); TX FEES + UserDiff; ASIC tested
by
TiborB
on 24/05/2013, 09:17:06 UTC

Let's give it some time - yesterday it took over half an hour to get self-fixed. Mine is off too:
18176    2013-05-23 19:51:28    2:06:53    17624457    1650    0.00108921    none    237567    25.58627000    90 confirmations left

and earlier when I looked (at around 19:05 server time) my score had just reset and showed almost zero (a few microcoins).

Possibly but its been more than an hour and the # of shares looks normal when its updating the shares usually increases.  I also noticed 20 minutes prior to it ending the numbers reset.

It's now been several more hours and at least for me the rewards haven't been recalculated although miner was working non-stop.

18176   2013-05-23 19:51:28   2:06:53   17624457   1837   0.00130912   237567   25.58627000    36 confirmations left

I guess it's just a bout of bad luck. Well, can't complain, with overall good luck yesterday, it's still profitable.


By the way - does anyone else have any issues with this one - I'm quite a bit short on it too:
18179    2013-05-23 20:42:16    0:15:23    1329197    202    0.00287789    none    237575    25.35675211    44 confirmations left


A little short on that too if I calculate the reward per share.

Block 18176 is off for many of us. Have been waiting for the rewards to get recalculated, then sent a message to Slush at the time when there were only 12 confirmations left.
The block just got confirmed, no adjustments. Obviously, it would be chaotic and unmanagable if everyone cries about blocks, and there should be a proper way to escalate these issues and get them addressed on time. In many cases Slush is able to intervene, but on few occasions the issue does not get fixed.

What would be the preferred way of bringing attention to these issues - especially given that the spam-rate on this thread is rather high so Slush might not be able to notice/catch posts.

Cheers,
   T

PS: dear trolls, I am not complaining about the quality of service Slush provides, but seek a way how he could be notified of pool related issues is a smart way - without highly redundant communication -  in the future. This topic would have been the proper communication channel but given the white noise...