Repository navigation
Conversation
bmuddha
added this pull request to stack #1797
October 12, 2026 04:24
bmuddha
force-pushed
the
stack/chainsync/cutover
branch
from
October 12, 2026 13:14
53dece6 to
e2cb420
Compare
bmuddha
force-pushed
the
stack/chainsync/cutover
branch
from
October 13, 2026 08:25
7623644 to
cd1ac62
Compare
Collaborator
Author
|
@coderabbitai review |
Contributor
|
bmuddha
force-pushed
the
stack/chainsync/cutover
branch
from
October 13, 2026 13:33
cd1ac62 to
9258666
Compare
bmuddha
force-pushed
the
stack/chainsync/cutover
branch
3 times, most recently
from
October 13, 2026 15:55
e36d2de to
8a138ef
Compare
bmuddha
force-pushed
the
stack/chainsync/cutover
branch
from
October 14, 2026 00:59
8a138ef to
0916317
Compare
bmuddha
force-pushed
the
stack/chainsync/cutover
branch
2 times, most recently
from
October 16, 2026 06:59
f5e2af3 to
67b7742
Compare
bmuddha
force-pushed
the
stack/chainsync/cutover
branch
from
October 16, 2026 13:48
82b7e02 to
72793c1
Compare
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.
What changed
Switch leader orchestration and Aperture acquisition to ChainSync. Aperture uses missing-only
ensurecalls and consumes theiru64fetch counts directly. Move provider and optional AML settings into ChainSync configuration, read Committor recovery sessions directly from persisted Engine state, and remove Chainlink, standalone AML, and the separate undelegation-request service.Update integration callers, configurations, launchers, and required fixtures together. Keep the legacy metrics crate and its surviving calls for the next layer.
Closes #1698
Closes #1748
Closes #1749
Impact
The legacy remote-provider configuration and CLI arguments are replaced by ChainSync configuration. Only leaders start synchronization and application services. Committor skips missing or stale local sessions without refetching them through ChainSync; nonce checks remain in its RPC path.
Reviewer notes
Reconnection and lifecycle replay remain best effort, without a startup scan or gapless-delivery guarantee. Local fixtures and workspace checks do not qualify live providers or remote integration deployments.