-
-
Notifications
You must be signed in to change notification settings - Fork 310
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
Optimize issuing advance engine fcU for prepare payload #4054
Comments
Right now PrecomputeNextEpochTransitionScheduler does not work after the merge due to that. I suppose we should make this work as a separate scheduler like in lighthouse and do precompute next epoch transition in this scheduler too https://github.com/sigp/lighthouse/blob/564d7da656803f5e06e53a303972580be54500bf/beacon_node/beacon_chain/src/proposer_prep_service.rs#L18 |
my idea is not NOT run or we do slot processing on a copy ? |
if you want to take this up @tuyennhv feel free! |
yeah we're on the same page, we only need 1 scheduler, yeah I can take this @g11tech |
Currently the engine fcU is issued just after a successful block import (#3965), predicting the new head to be the head in the next slot if BN has any beacon proposer. Normally this would work just fine, but this isn't sufficient and the following scenarios needs to be addressed:
The text was updated successfully, but these errors were encountered: