if you look at the numbers, there are quite interesting news!
on 7-12 the POS difficulty went down ( 15000 -> 5000 )
on 8-12 the masternode count went down ( 500 -> 62 )
i dont know if that is a bug on my client ( or as some would say "i abuse the network" lol ), or real numbers..
nevermind, my freshly minted coins arrive at Bittrex and i can trade them...
still 0.6 BTC available there to dump this coin!
This is how you were abusing the network (lol), your client saw only one (or two, I don't remember) masternode while there were dozens other active. Now it's better, your client sees 62 when there are hundreds other active. It's not a joke, it's a glitch.
Unfortunately I have also observed this case (althought not yesterday) so big decisions have to be made regarding 8BIT codebase. More TBA, although it has been already suggested here as necessary step.
What I have observed yesterday was a orphan storm just after I got my client responsible.
Masternodes are not connected directly to each node (that would be crazy), list of them is shared across clients. When network (of regular nodes) is quite small and "important" (accepting incoming connections, lot of connections) nodes disconnect, broken/partial list might be shared in part of network for a while Also masternode payments are not enforced therefore such problem is not detected immediately by masternode operators.
In case of PoS we need more staking power from other users, why do you people keep your coins on the exchange? A price will not explode tommorow.
However, unlike many other coins' issues, things I've just discussed are not serious threat for a network (real problem is elsewhere), so it's all about improving network strenght not a matter of life and death.
BTW ATM network diff is 11600 and everything looks fine, are you sure there was 15000?
