Quote from: StakeBox on October 04, 2016, 02:33:30 PM

OK, guys. I haven't read back through the past few pages yet, I thought I should just throw a post up quick to let everyone know what's going on. Here is a direct quote of myself on slack:

Yeah, I am just getting to the bottom of the issue. As jakiman pointed out the seesaw change didn't account for block 325500, that was a really stupid mistake on my part. We were able to get around that by having everyone restart their wallets, I made a fix locally and ran it, and then everyone else could sync past that problem. Now the problem is that everyone is banning each other because they are not accepting one another's blocks. If we see a different masternode count then we will calculate a different valid masternode reward and refuse blocks from people who don't agree on the masternode count. I have disabled masternode reward enforcement for now, that will allow us to get back on the same chain. The main problem is determining which chain to consider valid. I am resyncing right now to see where I get, I would advise everyone to do the same, I think that should put us all on the same chain. So, load up a blockchain backup if you have one and resync from there.

If you have removed the bantime line from your darknet.conf, or naver added it, please add "bantime=50" in there. That will allow for a quick unbanning of the peers you have recently banned unjustly, and help us all get back on the same page.

the chains we have been going off is the masternode info page. i have resynced them all to that. although from what i have seen there are a couple of others going but the

./darknet-cli getblockhash 325553

fca8b0fd86b80b6c5e966a0542f760c38b0752ad9b515f08f35f605530d754df

seems to be the one they sync into mostly which is the masternode info page sync

~~can we get confirmation that bittrex on the same chain before start moving stuff.~~

just done a test and bittrex on the same chain as well. we going off that one then ye?