Rationale
When I had first setup a polygon node, it worked fine for a while until a hardfork happened and it stopped working, it took me about 3 hours to get it back up and running after I realized that the binaries were outdated, Instead of throwing an error about "being out of sync", it'd be much more useful if it also logged a warning alongside that message about updates.
Implementation
What would improve this for everyone is some way for the binary to check for current releases along with upcoming hard forks, so that the error/warning that is currently displayed can be replaced by that.
- It can ping github releases once a day for and check the latest releases
- It can ping a trusted polygon labs operated sub domain to ping for updates
- We can eliminate the need to ping entirely by just updating the help message to have user check for updates additionally.
On another note, it was incredibly disappointing to see 2.10 Austin hardfork being released unannounced, the binaries for the same were released 3 hours later, I understand that there were security concerns but once all the validators had it updated on their end, 3 hours is a bit too much for downtime, ideally this should've been announced minutes after release as a known issue if the new source/binaries couldn't have been released any earlier.
Additional Notes
I am not sure if "chain out of sync" is the only error class that may benefit from the version warning system that's described in this issue, it would be wise to add and explore any further potentially useful warning additions that'd help node maintainers do their job faster with minimal downtime.
Rationale
When I had first setup a polygon node, it worked fine for a while until a hardfork happened and it stopped working, it took me about 3 hours to get it back up and running after I realized that the binaries were outdated, Instead of throwing an error about "being out of sync", it'd be much more useful if it also logged a warning alongside that message about updates.
Implementation
What would improve this for everyone is some way for the binary to check for current releases along with upcoming hard forks, so that the error/warning that is currently displayed can be replaced by that.
On another note, it was incredibly disappointing to see 2.10 Austin hardfork being released unannounced, the binaries for the same were released 3 hours later, I understand that there were security concerns but once all the validators had it updated on their end, 3 hours is a bit too much for downtime, ideally this should've been announced minutes after release as a known issue if the new source/binaries couldn't have been released any earlier.
Additional Notes
I am not sure if "chain out of sync" is the only error class that may benefit from the version warning system that's described in this issue, it would be wise to add and explore any further potentially useful warning additions that'd help node maintainers do their job faster with minimal downtime.