Any news about the fork ? All seems all right ?
How many masternodes were exclude from reward queue because not updated to 0.13.8.2 ?
This kind of thing was always responsibility of masternode owners, when your node goes offline from the network or you stop getting rewards then you know it's time to check up on things
But I am sure that people have scheduled this date at least 10 days before so no one should be surprised by this, maybe someone who is already on vacations somewhere without internet if that is even possible at the time we are living in.
I don't understand you.
The time between a fork (or a mandatory update) and it annoucement is only the responsability of the development team.
And this time must be enough to do the upgrade for each masternode owners : even more during holidays periods.
It is not enough to have access to the internet to update your masternode, you must also have all the information to access it, especially in terms of security (logins and passwords).
I have hundreds of longs passwords (not memorable, for security reasons) and I do not have them with me when I'm on vacation, even if I have internet.
To answer the question I asked, there are 900 masternodes (sources:
https://znodestatus.privex.io/ and
https://masternodes.online/currencies/XZC/) that have been banned from the rewards list following the fork: they lost their position in the queue and are waiting for their update. 900 masternodes out of 5000, I think that is a lot and is not at all respectful from the development team (which, I suppose, have all they masternodes in the 4000 remaining masternodes).
XZC is a fabulous project but the management of the mandotory updates is a real problem since the masternode begining.
