well still no answer from the late great captain.. Guess if you stick your head in the sand long enough you'll all just forget about this ever happening.. well come to find out slush should have been able to detect this long before now at the scale this attack was/is occurring. what he should do is compensate those that can prove they mined here from the time he announced support for xt(when the pool went down hill) and the time he announced that it was a block withholding attack.. here is an article for you to read slush since i know you read this thread.. http://organofcorti.blogspot.com/2016/02/detecting-unintentional-block.html

Looking forward to how you address this with those that lost their asses mining at your pool. > Why should the miner that had these problems be allowed to continue mining here?  Why should the entire pool be punished for this miners bad hw?  Shouldn't the miner have to compensate the pool for this unintentional or not?    And i find it funny that you have yet to tell us what miners(brand) they are and what software was on them.. Seems to me there is much more to this story than you are letting us know!.. If you want this to all go away im sure compensating the miners from your 50k a month youve been making on fees would go a long way in rectifying this situation along with the info on the attack for other pool OPS!.. Lets see who slush is looking out for!  Himself? or the community?

Best Regards
d57heinz

EDIT even funnier yet.. "By allowing the public to examine block hashes, Slushes pool will allow you to check for block withholding too. If they also include an anonymised user account identifier, the pool difficulty for that block hash and the number of block hashes returned by that user at that pool difficulty, you'll also be able to check for unintentional block withholding. I hope other pools follow suit."

Slush gets pool fees yet he expects us to babysit it for him. If it wasnt for a group of us letting him know this wouldnt have even been an issue. Slush said it was luck! FFS. what a joke.. slush needs to take some damn accountability here.. UFF WTF

30 hours 4 blocks . @ 60 % day and sub again ^^

32 hours 4 blocks . insane

Slushpool down ohh yeaaa . too much hashrate 56% pool luck day - Holy shit

You very much could be right. the extra strain merged mining causes could be part of it.For what nmc worth its a joke to even bother!  looking further back on his news and you can see that he started merged aswell just before this all went to shit.. So i feel its a number of factors but the greatest one being that he doesnt seem to give a shit about the damage he has caused and continues to inflict on the miners that still mine there(while he haphazardly works out the problems). Also he has yet to come with what brand miners supposedly had the bad code.. Should make for a good story there im sure!  if you look at the blocks found on the dashboard  click the nmc button on the top right of the graph and watch it for the next couple weeks.. Slush finds shit tons of nmc blocks. but what is odd to me is that the pool hardly ever finds a nmc block along with a btc block.. i could see once n a while being orphaned on nmc but its my understanding that nmc being about 1/4 the diff of btc you should almost always find a block of nmc when you find a block of btc  but with slush that isn't the case..  Most likely server issues or propagation issues with nmc as well..  I know about a month ago he was getting block notifications up to 30 seconds after the rest of the pools on btc(this alone attributes to 72 min of mining on old work every day for who knows how long!).. That's a shitload of lost work on old blocks!  anyway its like beating a dead horse at this point. Im working on submitting what im owed from sept to dec when i finally said hell with this i'm moving to kano. Good luck with this.. Hope your captain gets his shit together.. Just know that lost blocks due to bad luck in theory should hopefully get caught up with good luck.. but when its server issues and block withholdings.. you will never regain back your losses.

Best Regards
d57heinz

Two blocks appeared in less than 2mins ?

Sorry if i insult someone, but i think you should be brain dead to continue mining on slush and continue loosing money. I mean just look at the luck chart, look how much is your earning, look now how many blocks are found and compare that with the luck chart! And the last look when you will get strait answer or any answer from the so called Captain stealer!!!

Captain is sad; it is too hard to satisfy everyone.

wow hes online and only posted 2 small lines shows where his priority is

We detected the problem, fixed it, announced it publicly and right now we're preparing Hashrate Proof to let our users to check how the pool is mining. I don't think we can do more than this. To be honest, discussing *here* is not really constructive.

I have to disagree.  Telling your miners that we are in another period of bad luck for weeks while they lose 15-20% of their revenue is not honesty or character.  Honesty and character would be advising your miners that you suspect a significant issue with your systems and that they may sustain significant losses for a undetermined period of time.  In addition, what you are referring to as the "problem" is questionable at best.

At an absolute minimum, Slush's handling of this situation was awful and not representative of the standard you have set of transparency and trust.  The fallout from this incident has yet to materialize.  You will realize at some point that the cost of lost revenue from being up front with your miners would have been much less in the long term.

Slush is not being fully transparent about this issue.  There is not way you are and the fact that you continue to perpetuate this narrative is disappointing.