Quote from: maxcoinproject on September 06, 2014, 04:03:32 PM

Quote from: miningpoolhub on September 06, 2014, 03:59:59 PM

Quote from: maxcoinproject on September 06, 2014, 03:23:22 PM

Quote from: subSTRATA on September 06, 2014, 03:02:37 PM

Quote from: miningpoolhub on September 06, 2014, 02:40:42 PM

Actually checkpoint is not needed for hardfork. Hardfork don't need to be holding 51% major hash.

Not even major hashrate is needed for successful hardfork - what new nodes must do is ignore any node which does not comply to the new ruleset, it is as easy as that. Even
some coins laughed at by most people did it right (see Flappycoin, if node is not at least v3.1 it will end up ignored immidiately, you will never ever see it connect even for a split
second) but instead of just using what worked - which is what they did in the first place by cloning Bitcoin - so called developers opted for some untested techniques and stuff
that realy make no sense.

Unfortunately the wallet version was not updated with the client so we cannot do this until the majority of users has updated to the most recent fix. Once this happens we will ban previous versions.

Instructions for updating to the most recent version can be found at http://maxcoinnews.net/maxcoin-0-9-2-1-release/

I get this from getcheckpoint which is different what the link saying.

{
   "synccheckpoint" : "0000000000057faf782713f21104bffcfc8cc9107df88dea399b06ffe3e0d6c4",
   "height" : 557625,
   "timestamp" : 1408634353,
   "subscribemode" : "enforce"
}

Even after typing -resync.

That's actually fine. I've updated the link. It seems my client was still updating when I wrote the guide.

But the problem is that it is stuck. Cheesy

I need to sleep. I struggled with it whole day.