With these higher active masternode numbers we are moving to 6 or 7 days before MN payment,
thats excluding variation... so my guess is that either you are getting acquainted with Miss Variance
(who can be a bitch sometimes) or perhaps you did something* that sent your masternode back in the waiting line ?
* for example updating your cold wallet with masternode=1 in your dash.conf ? best to set masternode=0 in there if you are still using dash.conf
and want to update your cold MN wallet. To avoid this alltogether it is probly best to use masternode.conf .. that has not this specific "bug".
Hm, my dash.conf is empty. Could this be??? I don't remember editing this file in a long long time.
Another question: when I open the Dash client to synchronize with the blockchain will this have effect on the masternode?
check your masternode.conf, if that has your masternode info it is safe to sync the blockchain, you will not run the risk of getting set back in line...
for those of you masternode operators still using only the dash.conf make sure you put masternode=0 in there during sync of the cold wallet blockchain and change it to masternode =1 when a
protocol-change update comes out...