Skip to content
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

Check for forks less frequently and keep track of the highest level verified from the detector #924

Open
ivanopagano opened this issue Sep 29, 2020 · 0 comments

Comments

@ivanopagano
Copy link
Contributor

To store the latest level that the detector checked in previous cycles and when the next detection check is done, verify all the blocks in between...

This complicates a bit this phase and carries additional risks to be handled.

@vishakh: I'd like your opinion on how to best proceed. I'd suggest going on with this (strictly speaking: incorrect) solution, and add the corrected checking as part of the next train of changes related to handling missing cases of invalidation (i.e. big-maps handling).
But you might want to wait and handle this first and now.

Originally posted by @ivanopagano in #903 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant