I tried pointing my S9's at NiceHash, but am seeing a ton of rejects (30%). The S9's are behind a Stratehm stratum-proxy.

I've tried enabling and disabling extranonce, as well as setting a reasonable difficulty. Still tons of rejects.

I posted on the NiceHash thread, but if anyone has suggestions for here for getting S9's to work well with NiceHash, I'd appreciate the info.

I'm trying to point my S9's at NiceHash for SHA256 mining. I've got them behind a Stratehm stratum-proxy.

Unfortunately after running for about 30 minutes, I'm seeing a large percentage of rejects (around 30% now). The rejects seem to be duplicate shares:


I tried to work around this by playing with enabling and disabling extranonce and by setting a reasonable minimum difficulty. Nothing I change seems to help.

Any recommendations for reducing the rejects to a reasonable level?

It's too bad that nextdifficulty.com seems to be frequently stuck (like it is now). I've found it to be more useful for indicating the trend during a difficulty cycle.

It seems like they've always manually adjusted their price on the site. Maybe they're afraid of automatic adjustments and the affect of larger price swings.

Does the autotune function run every time you restart mining?

Is it actually hashing during the tuning time?

Seems like the firmware could cache the results of the last tuning in the local file system, then use it the next time instead of tuning all over again. To detect environment changes, it could flush the cache if there's a big temperature change.

Some people have scripts set to restart the miner software. If it takes an hour hit every time the miner restarts, that could be bad.

My S9's are hashing fine with the old firmware. I'm going to leave them alone.

Sorry, no. Solid connection for me in the US.

I've got B3 and B10 units. Here's my thoughts on installing new firmware.

Just say no.

I've found the best strategy is point them at a stable pool (I use Kano), leave them alone, and pray you don't lose a blade.

Phil, thanks so much for hosting this contest for so long. I was skeptical at first, thinking that predicting future difficulty was pure guesswork. That's why I made gentle fun by having our cats do the actual guessing

But I was wrong. This game was not only fun, it became an important center for discussing the future of mining.

I'm going to miss this, because to me this thread has become part of every difficulty adjustment. I (or rather our cats) will probably keep guessing now, even without the thread.

All that said, I completely understand that you need a break.

Thanks again for your efforts!

+5.1 = edonkey

As always, thanks Phil!

I woke up this morning to hash rate alert emails. Two blades in one of my S9s had fallen over with all x's.

When I looked at the proxy data I noticed that the hash rate drop correlated with a failover from Kano (the main pool which had a brief reset last night) to Zpool. I've seen this problem before with Zpool, but I thought I worked around it by specifying the starting difficulty.

Anyway, after a soft reset both blades came up. I also dropped the frequency a bit for good measure. The temps on one board (not the one that failed over) have been creeping up anyway with no changes at the data center.

I've also removed Zpool as a failover pool. Been burned by this problem too many times now.

Here's hoping that this was just a software issue and not an impending hardware failure...

Wow! Nice sleuthing!

I would have thought that they wouldn't sync their sources with a public repository until they're ready to ship. Let's hope that they're on the verge of an announcement.

+5.6 = edonkey

Jack, the talkative kitten that my wife is fostering came up with this number. Hopefully he's closer this time than last.

Phil, I really appreciate you running this contest for so long. It's been one of favorite ongoing threads on the forum.

That said, I understand that you need a break.

I think we'll all need a break after the next difficulty hits. It looks like it's going to be a monster increase...

Anyway, hats off to you and suchmoon (who originally funded the difficulty speculation game) for such a wonderful time!

Yeah! That is pretty damn satisfying!

Wow. At 381%, that was one tough block to poop out. It's as if the pool was constipated...

Glad it's over. Now time for a double (or triple)!

Well that was short-lived. The solo pool found a block, so it's a new race.

You're in first now zOU!

I checked my proxy and my S9s have been mining solid on kano without interruption. Also I got no low hash rate alerts from CKPool Monitor.

Maybe it was a temporary routing problem on your end?

Thanks! I saw that one of my sticks was in first place yesterday, but the forum was down.

I guess that large share (relatively speaking) will keep me in first for while, probably until the solo pool finds another block and resets everything. I'll enjoy it while I can

Yeah, I saw that huge share by JeffZwolle before. Incredible. Probably none of us will ever beat that...

I've mentioned this before, but it's possible use the "--balance" option in the "Manual options" section of Minera. The trick is that you also need to specify as many pool entries as you have workers. The downside is you can't specify a failover pool.

So if Morguk has two sticks (for example), then he'd specify two pool entries, both for the solo pool but with different workers (so they show up separately in the race).

It's lazy, I admit, but it does work. This is what I'm doing currently with my two sticks.

You're welcome.

I'm not really looking for tips. When I come across something cool I just like to share it.

Hope you get a lot of bitcoins someday