Yes I lost 25k which pisses me off and the POW phase listed was no where near what happened. So yes the first blame is on the devs and secondly the mining pool admins.
We notified users of a potential fork immediately after it was detected. Seconds before that, we attempted to contact dedicated via their IRC channel.
The StealthDevs are not responsible for mining pools. Our job is to make a functioning coin. Anyone who mines on a pool is at risk of mining on an orphan chain. That's a known caveat.
Your issue is completely with your pool operator for continuing to mine on an orphan chain after he had been notified that the pool was on its own chain.
In the future, please look at the record of your pool and mine on a pool that is attentive to the coins it is mining.
Edit:
https://bitcointalk.org/index.php?topic=681725.msg7784439#msg7784439This is something that people really need to take seriously, it's a double edged sword for everybody involved. Dedicated should shut down registrations when he gets too much hash, but at the same time in the past his chain is longer and the devs go with his chain and the least ammount of miners get fucked. But the problem comes when the exchange is on a different chain than dedicated, while dedicated has the most miners the exchange has the most coins (most of the time) and the most to lose so that is a tough choice.
Then there's the miners. Guys if your just mining with your own rig using a smaller pool (X-hash is the shit) is fine and you will get just as many coins, bigger payouts less frequently. BUT if you are renting you want the fastest blocks to maximize your return on your rental fee, so again tough choice.
I don't really have any answers other than if we all make an effort to spread the hash more evenly the block time should be about the same regarding rentals. Yeah i'm pissed I lost a bunch of coins and it would be cool if the devs offered some compensation but we all know that is not being realistic, I decided to go with dedicated because I rented hash and that was a gamble that didn't work out this time. so for the 1000th time spread the hash and dont pile on dedicated, if he wont be responsible and shut down registrations its up to us to stop the potential for forks. I think the dev's going against him this time may help him grasp the concept that what he is doing, while looking out for his miners is causing huge problems for all of us.
