Skip to content

Replace Chainlink with ChainSync #1698

Open
0 of 7 issues completed
Open

Description

@bmuddha

Scope

Chainlink's complexity makes account synchronization, update ordering, and recovery difficult to reason about. We need to replace it with magicblock-chainsync, a smaller service for acquiring base-chain accounts and keeping their local state synchronized.

Consumers should request accounts through ChainSync::sync, with sync_transaction_accounts handling transaction account classification. ChainSync should own remote acquisition, subscription lifetime, and delegation lifecycle observations, applying account images directly through Engine rather than exposing an update stream or returning account images to callers. Execution, account locking, storage, and lifecycle enforcement should remain Engine responsibilities.

The integration should remove Chainlink and the standalone AML crate, keep provider and optional AML settings in ChainSync configuration, and remove duplicate remote-provider configuration. Committor recovery should use persisted Engine state without depending on ChainSync.

Reconnection and replay should be best effort, with no gapless-delivery guarantee or startup account scan.

Related planning: magicblock-labs/dev-kanban#193.

Outcome

Validator workflows should use ChainSync instead of Chainlink for account acquisition and background synchronization, preserving Engine's account lifecycle safeguards with a smaller API and clear ownership boundaries.

Activity

  1. changed the title [-][Epic] Chainlink rewrite: minimal account synchronization[/-] [+]Rewrite Chainlink as a minimal account synchronization service[/+] on Sep 17, 2026
  2. added this to the v3.5.0 milestone on Sep 17, 2026
  3. added theissue type on Sep 19, 2026
  4. changed the title [-]Rewrite Chainlink as a minimal account synchronization service[/-] [+]Replace Chainlink with ChainSync[/+] on Oct 9, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

Projects

No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions