There are clearly several major issues on the network at the moment that I will be spending the day resolving. The first is that there is still a large number of people using the old client, causing lots of invalid blocks to be mined. The second is that a checkpoint on an invalid fork is floating around the network and needs to be invalidated: please leave checkpoints turned off until a fix is released. An update solving these problems will be released as soon as I can ascertain that nothing else is wrong.
If 1gh continues to mine on their own fork it will be a sad loss to the network.
Thanks for the patience guys.
Thank dev.
I think you'd better roll back to before the hardfork source code and just change block time and block reward.
This kind of forking problem didn't happen at recent maxcoin hardfork. So it doesn't look like just the problem of running new version peer rate.
I saw this situation some months ago with Darkcoin.
Currently dynamic checkpoint seems like to not working properly. I don't know where this checkpoint sync source code came from but even Darkcoin is not forcing this type of sync currently. They failed hardfork issue twice and changed to soft fork their blockchain. This kind of problem happened on Bitcoin also, and it needed several weeks to fix.
It's really not an easy problem on p2p. This kind of problem is hard to simulate on testnet and makes investors disappoint as time passes. This network breaking really harms maxcoin and its confidence also.I just recommend you to give up dynamic checkpoint sync, roll back main source code to before the hardfork and change block time and block reward. This is safe, and makes things smooth.