forked from ChainSafe/lodestar
-
Notifications
You must be signed in to change notification settings - Fork 0
feat: add Gloas payload status to node notifier #18
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
Closed
Closed
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
d360bbd
feat: add Gloas payload status to node notifier
lodekeeper c2ec5c8
Merge remote-tracking branch 'origin/unstable' into feat/gloas-notifier
lodekeeper fdd80f4
feat(notifier): shift log point to 5/6 of slot in gloas
lodekeeper e399634
refactor(notifier): express log point as BPS
lodekeeper File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.
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.
I feel like this shouldn't be pending ever, we might need to re-think how out notifier works in gloas, my intuition right now is that instead of printing the log out half way through the slot we should rather do it at 10 seconds (or so) in the slot, and then either print out full or empty. what do you think @lodekeeper ?
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.
Agreed, good catch. Pushed
fdd80f44d0: in Gloas we now log at 5/6 of the slot (10s on mainnet 12s slots, 5s on future 6s slots) instead of halfway. Pre-Gloas keeps the half-slot cadence to avoid shifting existing behavior.Rationale for 5/6 rather than a fixed 10s: PTC votes land around 2/3 of the slot, so 5/6 gives ~2s margin for proto-array to update the head from PENDING → FULL/EMPTY. I kept the PENDING branch in
getGloasExecutionInfoas a safety net (e.g. if PTC quorum never lands), but it should be rare at 10s.