-
Notifications
You must be signed in to change notification settings - Fork 202
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
ShufflingRef approach to next-epoch validator duty calculation/prediction #5414
Conversation
53836dc
to
5bd24dc
Compare
58d690b
to
2cea1ee
Compare
0cd3098
to
910f983
Compare
…roposers; refactor maybeUpdateActionTrackerNextEpoch to be separate and reused function; add actual fallback logic
…nalties and MAX_EFFECTIVE_BALANCE to ensure rewards don't matter
From a variation of that (
i.e. it matches exactly, in mainnet conditions, even without all the guard conditions, which are not at all tight bounds. |
On
so, same network conditions, same host, over about 3 hours on Holesky even with the cautious guard/failsafe conditions, it removes 2/3 of the epoch-lookahead Each had taken about 1.7 seconds:
during which the main Nimbus event loop had been blocked, once per epoch. It's possible to gradually loosen/broaden the conditions under which |
No description provided.