It looks like I failed over.

Edit: on both nya & stratum.

Just watching the % count up...

222.22

Man, guys... New mining location still seems to be too hot even though its exhausting out a dryer vent... Hashing has dropped from 3.75 to 3.0... It must be too hot in the back room of our new house.

Looks like sidewinder tracks... 2222222 !! 

Mine on, time for a May Block! 

If you look at the pool stats, this pool hasn't found a block in quite awhile.  IIUC it's because the pool has a small fraction of the mining power of other pools.  When it hits, it should hit big, but you will also be sharing that bounty with everyone who's been mining up to that point.  The pool fee is pretty small and very reasonable, from what I've seen.  You won't get regular payouts though, unless a LOT more miners join the pool.  I've been using slushpool.  It's pretty regular and if you watch that, you can get a feel for how this all goes, statistically.  I think the fee there is about 2% though.  I really like and support the idea behind this pool - it just doesn't work for me right now.

Hello, i want to obfuscate the traffic from my miners to slush pool using tor, i have routers with openwrt/lede and tor activated, but i'm using slush pool normal addresses, i read that slush has a hidden service for the pool, how do i set up that for my miners?.

Thanks for any orientation you guys can give me.

Yes you did
(and it's cleared)

It's not once, and it's not the wrong button.
It means you mistyped something, e.g. got your username wrong or password wrong.

Bitcoin mining is like banking - lots of money involved - thus web site security is a top priority.

However the site is very aggressive as banning certain things, coz if it wasn't, the web site would be regularly dead due due to DDoS attacks.

However, PM me your account or IP and I can clear it.

Luckily I have full coverage because the guy driving the car that hit didn't speak any English and had none. Everyone is okay, thanks for asking.

I understood from the S9 thread auto tune is in software - you can drop in the fixed frequency firmware from Bitmain and fix the frequency lower for the auto tune S9's...only useful if you want to reduce temps (and hash) from what I gather

The s9 b23 at my main farm is also back up. Sorta.
Replaced the control board with one from a batch-13 (non-auto tune) that I had been using for spares. Works perfect and even better yet now that Frankenstein once again has Freq. control

Yep you got it... anything I need to know that I might have missed in the almost 2k pages of this pool?

Got my 41 TH just added to the pool last night , glad to join this community as I've been lurking here for a while and waiting for these miners to arrive and get setup!  Cheers, let the ramp up begin!

I'm thinking about switching back to Kano pool, how have things been guys? Everything still working good?

So I'm pretty sure there's a bug and I got paid 2 much. My N average was calculated from when you ran all of the shifts instead of when the block was found. My N average was only 330TH when block was found but I got credit for 412TH

FYI If anyone wants to know...
If you are doing electrical work while renovating, and arc a couple wires causing a breaker to flip, check your S9's  as for some strange reason it stopped hashing.  It was on a different circuit, was still on, but showed 0.00 TH/s   A reboot fixed it.

Very sensitive thing.  Maybe this is why others are having issues due to power fluctuations in thier neighborhoods.  Just an idea.


ZzzZZzAaaaapppp

All back up again finally - at 9:05 UTC

When KDB came back up, no stats were getting to it from ckpool - then ckpool deadlocked itself and crashed.
This of course meant a failover to your backup pools, then fail-back would have started at 9:05 UTC

This cleared up all the remaining problems since both KDB and ckpool had now restarted - and now all is going ok finally.