This article was first published on Horizen
In the continuing push to secure and improve the Node Tracking Systems, the following changes are being deployed. Some of these changes were previously deployed and reverted due to issues outside the tracking system. Additional updates and fixes were incorporated into this current build resulting in a more extensive update. We ask the node operators to monitor and report any issues.
NODE TRACKING SERVER UPDATE
All Secure and Super Node Servers will be updated on the weekend of September 21/22. Short periods of unavailability of individual tracking servers are possible. Nodes will fail over to different servers and no impact on earnings is expected. No action is required by node operators and any unjustified downtimes/exceptions caused by the maintenance will be excluded.
Some of the significant fixes and changes are:
Some challenge Exceptions were not closing if more than one existing was left open due to timing issues.
Ensure credit is paid to the proper stake address (from previous stake change restriction updates)
Handle bursts of DNS errors from misconfigured nodes that were causing a memory leak
In some rare cases multiple overlapping down times would not be calculated properly resulting in some nodes having extra up time.
Cert Exceptions now have a minimum threshold of 3 minutes (like Downtimes) before counting against earnings. Unlike Downtimes, short duration Exceptions are created and flagged with an ‘x’ status (excluded from up time calculations) if under the threshold to help with trouble-shooting. The email alert is sent if over the threshold.
Enhanced node connection checking. There have been some recent node tracking system exploits from dishonest node operators that these enhancements should counteract....
To keep reading, please go to the original article at: