-
-
Notifications
You must be signed in to change notification settings - Fork 289
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
feat: introduce proposer boost reorg to fork choice #6581
Conversation
Performance Report✔️ no performance regression detected Full benchmark results
|
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.
looks good to me overall, dropped some minor comments
d81491b
to
12c602d
Compare
12c602d
to
24353b6
Compare
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## unstable #6581 +/- ##
============================================
+ Coverage 61.49% 61.70% +0.21%
============================================
Files 556 556
Lines 58895 58799 -96
Branches 1856 1886 +30
============================================
+ Hits 36216 36283 +67
+ Misses 22638 22475 -163
Partials 41 41 |
|
||
if (prelimProposerHead === headBlock && prelimNotReorgedReason !== undefined) { | ||
return {proposerHead, isHeadTimely, notReorgedReason: prelimNotReorgedReason}; | ||
} | ||
|
||
// -No reorg if we are not proposing on time.- | ||
// Note: Skipping this check as store.time in Lodestar is stored in slot and not unix time |
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.
remove this comment
Motivation
Lay ground work for proposer boost reorg.
Description
timeliness: boolean
field to ProtoBlock to indicate if block was arrived on time or notgetProposerHead()
that will be used to determine which head block to build on when proposing blockpredictProposerHead()
to predict which head block to build on when proposing in the next slotPart of #5125