-
Notifications
You must be signed in to change notification settings - Fork 7
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
Update finalizer safety information file based on vote evidence from received blocks #135
Comments
heifner
added a commit
that referenced
this issue
Jun 6, 2024
heifner
added a commit
that referenced
this issue
Jun 7, 2024
heifner
added a commit
that referenced
this issue
Jun 10, 2024
heifner
added a commit
that referenced
this issue
Jun 10, 2024
heifner
added a commit
that referenced
this issue
Jun 10, 2024
heifner
added a commit
that referenced
this issue
Jun 11, 2024
heifner
added a commit
that referenced
this issue
Jun 11, 2024
Update finalizer safety info file based on received QC
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Depends on #259.
If a node deletes their finalizer safety information file, they may lose critical safety information such as the block they should be locked on. But in some cases, this information can be recovered based on the evidence in the QCs attached to blocks that the node receives from peers.
When processing a QC in a block, the node can check to see if any of the finalizer keys it manages are represented in the QC as a strong vote. If so, it can determine (by looking at the history of QC claims within that branch, which is stored in the
finality_core
) which block (ID and timestamp) the node should have been locked on due to casting that strong vote. If that block is more recent than the current lock in the finalizer safety information file for that finalizer key, then the lock should be updated.The text was updated successfully, but these errors were encountered: