How is it stuck in the first place?
Doesn't the fix that was already done for that problem way back when it happened to namecoin actually work?
-MarkM-
Was there a fix? I only remember "merge mining" saved it from death
Of course there was a fix. Namecoin itself might not have bothered to use the fix if they thought merged mining would cause them not to need the fix, but there were lots of blockchains around back then too and not all of them wanted to be able to be merged mined, or thought that even if they did adapt merged mining they might as well also use the fix too just in case.
It is why all or almost all coins from back in that era do not use bitcoin's difficulty adjustment algorithm; it is vulnerable to this problem so a more-adaptive adjustment system was made.
In actuality I think more than one fix was made, though I am not sure if both worked or, since suddenly we see new coins suffering the same old problem, whether either of them actually work. Which fix did this coin choose? Because whichever of the fixes it chose apparently is not the one that works, if indeed any of the fixes actually work.
For example, DeVCoin and GRouPcoin both use the same fix. I am not sure which other coins use that fix nor which used a different fix. But if this coin used the same fix as DVC and GRP and is still having this problem both DVC and GRP will be needing whatever improved fix this coin comes up with.
If this coin used the other fix, or tried to come up with a totally new and different fix, DVC and GRP might be fine using the fix they already use and only this coin and whichever coins are using the same fix this coin uses will need updating with some other fix or updating to use the fix that seems to have worked fine so far for DVC and GRP.
(Both DVC and GRP can be merged mined, but they have the fix too anyway so as not to rely only on some theory that somehow being merged mined is some kind of protection from this. I heard Slush's pool dropped namecoin, has that hit namecoin with this problem? Or does namecoin have the fix? Or is just the one merged mining pool no longer merged mining it not really enough of a drop in hashpower to cause the problem in the first place?)
-MarkM-
EDIT: If this coin has none of the fixes for this, does it also maybe not have a fix for the timetravel exploit? As the fix GRP and DVC used included the timetravel exploit fix while it was in there fixing this problem too so the one update/fix fixed both problems with one patch/change.
