[4+ EH] Slush Pool (slushpool.com); Overt AsicBoost; World First Mining Pool

[slush]

actually whitelisting isn't necessary, normal traffic is passing thu also, but whitelisted IP don't need to pass filter.

Now is adding new IPs to whitelist not possible as I exported that whitelist to ddos mitigation company, sorry.

[slush]

My 'Have you slept yet?' comment was much more a sympathetic gesture

Lol, I personally understand it wasn't a real question. However I'm considering this in real life, because attackers are using those information.

[pekv2]

I'm done with mining for a week or when ever these people stop their bs. It's a hassle, I'm pool hoping like a bunny hopping from a hunting dog, all pools are getting hit on and off, so its to tell which one to stay at.

I'm gonna send a donation your way, Slush, in a bit, it's won't be much as I'm mining with two cards and pools going down etc. Very angry at these criminals. I could not imagine you patients because I have very little.

[digital]

I'm done with mining for a week or when ever these people stop their bs. It's a hassle, I'm pool hoping like a bunny hopping from a hunting dog, all pools are getting hit on and off, so its to tell which one to stay at.

Yeah, once I saw that multiple pools were hit I just pointed my miners @ slush and stayed there.  I don't have the energy to keep up with all the hopping.  At least that way whenever the pool is up, Im mining.  And its looking like the worst is over now anyway.

[pekv2]

I'm done with mining for a week or when ever these people stop their bs. It's a hassle, I'm pool hoping like a bunny hopping from a hunting dog, all pools are getting hit on and off, so its to tell which one to stay at.

Yeah, once I saw that multiple pools were hit I just pointed my miners @ slush and stayed there.  I don't have the energy to keep up with all the hopping.  At least that way whenever the pool is up, Im mining.  And its looking like the worst is over now anyway.

Reason why I completely gave up, is that, no matter what pool I goto, Slush's or any other is, I'm getting massive connection problems. Not the pool operators fault as we know it. Prior of the attack everything was dandy, now it's just a huge cluster.

[thehairymob]

My miner keeps disconnecting slowing me down. Hope it get sorted soon.

[michaelmclees]

My miner keeps disconnecting slowing me down. Hope it get sorted soon.

That's what mine is doing.

[Thndr]

I have my miner pointed at a few different pools so if one goes down, the others pick up the speed.

Sure it spreads my coin around and I'll have microscopic amounts laying in some pools, but it'll keep my income stable.

[slush]

Please restart your miners; DNS changed again and some miners don't resolve them once again during operation.

[michaelmclees]

Please restart your miners; DNS changed again and some miners don't resolve them once again during operation.

Seems to have solved it.  Excellent work as always.

[slush]

Seems to have solved it.

It isn't first time today why it seems solved .

[slush]

Pool rounds #8393-#8396 has been recalculated using proportional (share based) mechanism to don't beat those miners who failed to connect on the end of rounds.

[Iyeman]

only 50 more blocks before the pool has mined 30k NMC lol damn ddos messing up the timetable for nmc accounting

[Portnoy]

Please restart your miners; DNS changed again and some miners don't resolve them once again during operation.

Tried shutting down and then restarting guiminer...
tried rebooting the computer...
still getting  "Problems communicating with bitcoin RPC"

[Seraphim401]

Good job on getting the pool stable again Slush.
I do have one small request though.Could you please make a userbar code available for the pool?
No rush  

Edit:The one in my sig only works when SSL is off 

[slush]

Good job on getting the pool stable again Slush.
I do have one small request though.Could you please make a userbar code available for the pool?
No rush 

User bars aren't a problem; problem is that pool is calculating hashrate using current round only, which is insanely inaccurate on round start. So I need to rework hashrate calculations to make userbars useful...

[kohlersc]

Having issues connecting again.  Is it me this time or are there still some problems?

[slush]

Tried shutting down and then restarting guiminer...
tried rebooting the computer...
still getting  "Problems communicating with bitcoin RPC"

Although attack seems to be gone, there are still some minor issues making connection less stable, which will be here for few hours.

However this should not affect mining hashrate so much, at least with miner which support long polling and NTime rolling (poclbm, GUIMiner with poclbm core, cgminer). Thanks to this, mining isn't stopped on share submitting latency.

[vapourminer]

so where should I point my miners?

cant connect with: api3.bitcoin.cz:8332, api.bitcoin.cz:8331, or api.bitcoin.cz:8332

all fail to connect, and cgminer keeps trying them as its the primary pool with no luck.

I may be on another IP than before the attack; Im on 3G wireless internet (USB modem). it changes IPs every 24 hours I believe. could that be the problem?

Ive restarted the miners many times in the last few hours to no avail.

I cant get to your website either.

[kohlersc]

I'm in the same boat.  Was able to connect on and off earlier.  But now I am just getting continual connection errors.