fix(consensus): wait for execution layer to be ready before driving it - #7230
Merged
SuperFluffy merged 15 commits intoAug 28, 2026
Merged
Conversation
decofe
requested review from
SuperFluffy,
hamdiallam and
joshieDo
as code owners
August 19, 2026 13:47
decofe
force-pushed
the
centaur/gate-consensus-executor-checkpoints-1787146458
branch
2 times, most recently
from
August 25, 2026 13:56
c3bfa01 to
57c0e9e
Compare
decofe
changed the base branch from
main
to
centaur/remove-executor-pacing-1787665736
August 25, 2026 13:56
decofe
force-pushed
the
centaur/remove-executor-pacing-1787665736
branch
from
August 25, 2026 14:04
e24ce0e to
6d34fd7
Compare
decofe
force-pushed
the
centaur/gate-consensus-executor-checkpoints-1787146458
branch
from
August 25, 2026 14:07
57c0e9e to
3bae36f
Compare
decofe
force-pushed
the
centaur/remove-executor-pacing-1787665736
branch
from
August 25, 2026 14:16
6d34fd7 to
c90f992
Compare
decofe
force-pushed
the
centaur/gate-consensus-executor-checkpoints-1787146458
branch
from
August 25, 2026 14:18
3bae36f to
76341fc
Compare
SuperFluffy
force-pushed
the
centaur/remove-executor-pacing-1787665736
branch
2 times, most recently
from
August 27, 2026 13:04
62bae04 to
bd09ca3
Compare
decofe
force-pushed
the
centaur/gate-consensus-executor-checkpoints-1787146458
branch
2 times, most recently
from
August 27, 2026 14:07
90d955d to
aecf550
Compare
Base automatically changed from
centaur/remove-executor-pacing-1787665736
to
main
August 27, 2026 14:13
decofe
force-pushed
the
centaur/gate-consensus-executor-checkpoints-1787146458
branch
3 times, most recently
from
August 27, 2026 15:00
e46b1fe to
44428f7
Compare
Co-authored-by: Derek Cofausper <256792747+decofe@users.noreply.github.com>
Co-authored-by: Derek Cofausper <256792747+decofe@users.noreply.github.com>
Co-authored-by: Derek Cofausper <256792747+decofe@users.noreply.github.com>
Co-authored-by: Derek Cofausper <256792747+decofe@users.noreply.github.com>
Co-authored-by: Derek Cofausper <256792747+decofe@users.noreply.github.com>
Co-authored-by: Derek Cofausper <256792747+decofe@users.noreply.github.com>
decofe
force-pushed
the
centaur/gate-consensus-executor-checkpoints-1787146458
branch
from
August 27, 2026 15:37
44428f7 to
580731c
Compare
SuperFluffy
reviewed
Aug 27, 2026
decofe
force-pushed
the
centaur/gate-consensus-executor-checkpoints-1787146458
branch
2 times, most recently
from
August 27, 2026 15:48
5e45b62 to
a4cb90d
Compare
Contributor
|
cyclops audit fast |
tempoxyz-bot
left a comment
Contributor
There was a problem hiding this comment.
👁️ Cyclops Review — No actionable findings.
klkvr
approved these changes
Aug 28, 2026
github-merge-queue
Bot
removed this pull request from the merge queue due to failed status checks
Aug 28, 2026
SuperFluffy
deleted the
centaur/gate-consensus-executor-checkpoints-1787146458
branch
August 28, 2026 15:46
This was referenced Aug 29, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Waits for reth to be ready. When starting from a fresh snapshot, reth will rebuild it indices. The cleanest way to check for readiness is to issue a non-destructive FCU using the latest reported EL state. Once it returns VALID, the node can start interacting with it.
This removes the need to retry finalized blocks because we might have caught reth while it was still rebuilding its indices, and as a consequence returned
SYNCING.