-
Notifications
You must be signed in to change notification settings - Fork 68
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
IF: Don't drop late blocks #2159
Comments
I believe |
heifner
added a commit
that referenced
this issue
Mar 1, 2024
heifner
added a commit
that referenced
this issue
Mar 1, 2024
heifner
added a commit
that referenced
this issue
Mar 1, 2024
heifner
added a commit
that referenced
this issue
Mar 1, 2024
heifner
added a commit
that referenced
this issue
Mar 1, 2024
heifner
added a commit
that referenced
this issue
Mar 1, 2024
heifner
added a commit
that referenced
this issue
Mar 1, 2024
heifner
added a commit
that referenced
this issue
Mar 1, 2024
Resolved by #2274 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently, any blocks received while producing a block are dropped and not evaluated. IF includes QC info in block extensions. Do not drop blocks, but rather incorporate their QC info into the
fork_database
. Do not automatically abort block but incorporate the block into thefork_database
for use in best fork evaluation. If LIB advances such that current block being produced is no longer built on LIB, abort the block immediate, re-evaluate best fork, and build block off the new best fork.Related to #2125
The text was updated successfully, but these errors were encountered: