The problems syncing could be due to problems with checking the proof of stake, or verifying blocks.
I set up one node to sync using "connect=" from 5 masternodes that are on the same chain.
I assume the masternode would all send the same block updates and there should be no differing headers)
The syncing got stuck about 100 blocks from where the masternodes were. (stuck on block 261687... 9278bbfb89902faee60e0b1a44d6b53616915168aae893b7d8c2ef4e1268aa60 )
If one is not able to sync from 0 blocks (without downloading a blockfile), reliably, then something is seriously broken.
It would be interesting to know if master nodes are paying on the chain that the are on only, or both chains. I haven't looked into how masternodes work in detail,I suppose they check, sign and send transactions based on the fork that they are on, and these are verified by other masternodes based on their version of the chain. Also, it's possible that a masternode can exist on one fork and not the other if it's transaction has been spent on one chain and not on the other or if the masternode transaction only exists on one fork (created after forking).
So we end up with masternodes disagreeing.
DarkCoin / Dash has had at least this fork:
https://www.dash.org/forum/threads/issues-with-masternode-payments-fork.858/I noticed that these messages stop appearing in the logs when the syncing freezes:
2016-08-11 23:13:54 UpdateTip: new best=55e6a5b9629e9a8bb8c00e43079857d6db2f832b5fdcf0a69e060c4dadadf564 height=260824 log2_work=55.897618 tx=370493 date=2016-08-11 02:55:27 progress=0.978356 cache=108387
My guess is that at some point there are too many orphan blocks to sort out and it becomes impossible to proceed.
DEV TEAM UPDATE
Basically, new v2.0.2.0 network was going strong for first 5 hours before a bad chain got pulled in by someone and ruined it all.
So the devs are currently working to end this fiasco of forks once and for all. If you know you can help, please PM s3v3nh4cks.
As expected, all the Masternode & Stake payments post-PoS block 259200 may be rolled back to ensure it's fair to all.
We are treading on uncharted waters here as DarkNet is first crypto to have PoS on Bitcoin Core 0.10.x. So hang tight!
Good to hear! I think a roll back to 259200 would be fair. (At least, it would prevent having to choose a chain and associated disappointments)
I'll stop digging through git and sleep.