Wehey! 1 day 4 hrs .... ! Whew!

^^^^ The bravado of the Americans .... OK captain, take counter measures!

Somehow, I can not seem to derive much confort from that at the moment .... never know, may come good!

This is a first for me. I've had a 23hr block here before, but NEVER a 24hr+ block.
If only Slush himself could come clean and tell us what gremlins he's introduced to that backend ......

EDIT:
They say a picture says a thousand words .... mervel!

EDIT:
END EDIT:
On your way out, don't forget to pay your bill!

^^^ Hehehehehheeee! But you never finished the joke .... surely the dick must have fallen off the horse!

No biggie there; to err is human.


Interesting here that no mention was made on the security flaws that were inherent in the version bitmain were shipping ... or are we supposed to assume that since he helped with the driver he must have forced them to plug the security holes too.

I think the community needs to get on bitmain's back to release not just the cgminer source, but the firmware source they run on their controller cards for the S1, S2, S3 and S4 (but mostly / pertinently for the S1 and S2 since they have now declared them end of line). I believe there are optimizations that can be made to the firmware code too.

Forgive the ignorance, are Block Erupter Tubes Antminer rigs? I think that message from ckolivas does not refer to the cgminer STILL being shipped by bitmain (potently loaded with the stratum redirection vulnerability, to mention but one security flaw).

Actually if they do have an issue, then I'd expect Bitmain to come clean before I will even consider an S4 any further. Scary stuff that unless you are having them host the thing .....

Some updates on the site.
You can now set the minimum difficulty for a worker (and having tested it, it works!).
And what a bummer about block 325164 ... I was already counting my chickens!

If it is better than before, then you are making some headway. The falling hash-rate, like I always want to think, may just be a more difficult (no proof of this, just my thinking) block we are on so you are better off getting the picture / speed after at least 24hrs.


I am glad that you have taken over that mantle! Slush always seemed to do this to me, though of late, not so much ..... but now I know why, YOU!

In my experience (and use), when / if the pool-side speed is within or above the expected, I tend to ignore the x. I actually have an S3 (though overclocked to 262.5) that from time to time gives the a couple of x's on the first chain and on other occassions one x on the second chain. My solution ...? I added a line to the scheduled tasks to reboot after every 8 hrs (that was after observation of the pattern of the x's appearing!).


My point exactly above (with regard to the x disappearing after reboot). Bummer that you had to re-do the paste, but since the S3 units to some extent are unique, that seems the only way you can get a solution for any individual unit / batch. Still, if all fails for now (and I were in your position), my last throw of the dice would be the blue wire hack, aka both fans at full pelt!

PS. If you get the chance to re-do your rig and detach the board from the big heatsink, could you clean the area in the middle behind the heat sensor chip? As in remove all and any paste that may be there (that will mean (I hope) the sensor will detect higher temps and thus run the fans faster).
EDIT: - aka in lieu of the blue wire hack!

It may indeed be the powering but that PSU should be very confortable running 2 S3's at stock (even overclocked within reason!).
That you get an x when you clock to 225 is rather telling though. If this is one of the very early S3's, did you get a chance to re-apply the heat paste?
I mention this because with one of my upgraded S3's (from S1), I used heat-pads rather than paste on the chips, and intitally some of the pads moved slightly from the chips when I was adding the heatsink; that unit kept "throwing up" and x now and again, and after updating to 4.6.1 it became a "main-stay". I decided to check the rig, unscrewed the heatsink and discovered what I mentioned above, aka the slipped heat-pads. I put them in place and added a bit of paste to the back and the x is now history (well, its only been a few days, but it has not appeared again ..... yet).
So it may be the case that if you have an early S3 (which were notorious for too much paste or non at all!) AND the unit was hashing OK before applying 4.6.1 then it is worth investigating that, otherwise I'd say 4.6.1 does not suit that unit.

Are you powering your rig properly and is your HW rate "normal"? I'd not worry too much about the 5s rate, as it can shoot all the way up to (in my case) 650, the key one is the avg rate. 438 seems low, but it "should" pick up in time (mine usually take 45mins to an hour to reach their peak avg).
PS. Also, what is your ambient? Do your temps look OK?

The UI will still say version 3.12.0 though I cannot recall how to return the correct version after you have updated. I vaguely recall you have to check via the SSH command line by issuing a call to the API (check the S3 Support thread, it is mentioned there).

Right, about time I had some kip (getting to 1 am this side of the pond).
Will look at those numbers more closely (wishfull on my end I have to say) in the morow!

Unless you are looking to liquidate your BTC for whatever reason, I'd hang on to it till next year. I definitely will be above that and a bit (of-course, I am not god, but I believe BTC will strengthen a lot in the next few months)

With that hashing power, I'd have my own solo pool (using the ckpool code) and a P2Pool node. Would definitely mine solo every other fortnight for at least a week depending on fortnight's earnings.

FORGOT TO ADD: - At current difficulty (different animal next year!)

Bummer!

^^^^ No doubt, you have enough space!
And neither am I so conversant with the merits of either, nevertheless, despite being in a different league than you are in terms of hashing power, I'll be running a node when I get my puny S4's on board!
BTW, you also may be ripe for mining through a proxy, but again not much guidance from this end!

EDIT: -Did you just see that? We won a 4 second block!

EDIT2: - Nooooo! Same block number!