So, I have a small amount of info as to what is happening:
08:47:13

getchaintips
08:47:13

[
{
"height": 56794,
"hash": "b6309b95902c56470ef27a4442df5db0860e1cc3854db230cb6ede10eef6d906",
"difficulty": 0.01837265411190288,
"chainwork": "00000000000000000000000000000000000000000000000000002f88fdc59002",
"branchlen": 0,
"status": "active"
},
{
"height": 56057,
"hash": "6988dfa709707d99ae448da5984be132fdb7f13e274c00be9fb605f32dabac1f",
"difficulty": 0.007104095844318024,
"chainwork": "00000000000000000000000000000000000000000000000000002f80151d1740",
"branchlen": 1708,
"status": "headers-only"
}
]
We have two chains : 56061 and 56794.
Heres what is funny about it: The shorter chain has the masternodes synced on it and in agreement, but less chain work.
The longer chain has more chain work (notice its diff is .01 while the masternode chain is .007). So the controller wallets pick the chain with more work, because thats part of the active-chain setbestchain rule, however the masternodes have banned those nodes already and prefer their own chain (primarily because of our rule to enforce sanctuary payees in a ranked list, which is part of Dash).
So its kind of interesting that the only way out is for me to blow the chain away and resync.
My question is, if we had the prod chain where obviously all the miners would be mining, and diff would be 10,000 instead of .01 will we stay synced on the chain with the most work in prod? It SOUNDS like we would, but ..... lets keep thinking about this.