-
Notifications
You must be signed in to change notification settings - Fork 977
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Report drifting close time on local node #4101
Conversation
ea69e1a
to
94b1721
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, just a few questions.
94b1721
to
c454827
Compare
@SirTyson PTAL. I re-worked the approach a little bit: now validators compare their own close time used for nomination with close time externalized by the network. If the drift is over a certain threshold, we fire a warning. This approach is based on the assumption that most validators on the network have healthy clocks. It also catches both drifting behind and drifting ahead, so no more special-casing is needed. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, just a few nit pics.
c454827
to
3b2b2d9
Compare
…se time with close time externalized
3b2b2d9
to
c712fe8
Compare
Resolves #1815