I don't think they updated (yet?) but if they do it's most likely going to be CryptoNight v7.

Great timing, mezonexuca. Also, it's nice to see someone who shares my point of view on how grossly mismanaged this (theoretically decent) coin is.

The post timestamps are too close together for this to have been posted in response to your post though (unless they prepared the post and had it on waiting). I think they either pushed the fork before having a formal announcement (which I understand, since it's time critical) or there's some bureaucratic hangup behind the scenes that we don't know about.

I too wish there were more technical details about the nature of this hard fork. We already know the difficulty algorithm is lwma, but the "emergency difficulty recovery feature" looks like a spontaneous reaction to the recent network issues. It might have been developed specifically for this case.

This is definitely relevant for pool owners. Either there's a pool owner update still in the pipe or they straight up forgot to mention this.

This isn't just frustrating. This is a dealbreaker. You cannot just show up here and make a post encouraging us to vote for this coin before you have even addressed the current issues. You cannot deny that this is a problem with the coin itself any more, so come clear. What is going on?

Also, you have yet to give us an estimation as for when it will be fixed. Next week? This month? ASAP? You're grasping for straws and you know it. Again, come clear. Heavily sanctioned vagueposting won't help you.

I do hope they're not this silly. After all, they already have a massive 40% premine. (I'm still hoping that at least half of that goes out in airdrops, by the way.)

To the devs: At least be honest with your promises and remove "asic resistant" from your website please. People should know what they're in for.

So I've given this coin a good hard stare because I love CryptoNote and this one sounded like it could actually become something. But I'm a sceptic at heart, so I waited a bit. And oh boy, good thing I did.

Your coin just got attacked and you don't even dignify your dwindling user base with a statement beyond "oh it's fixed." This isn't a trivial fix, so I bet you just manually paid out everyone and hoped the whole thing wouldn't repeat itself. Guess what: It won't work that way. It's bad enough that you're apparently not planning to go with the CryptoNight v7 fork, apparently you also flat out refuse to make any sort of statement about the state of your coin.

Verdict: Good idea, grossly negligent devs. Not mad, just disappointed.