[go: up one dir, main page]

Skip to content
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

Interop: op-supervisor local-safe data-ingestion from op-node #12077

Open
protolambda opened this issue Sep 24, 2024 · 0 comments · May be fixed by #12094
Open

Interop: op-supervisor local-safe data-ingestion from op-node #12077

protolambda opened this issue Sep 24, 2024 · 0 comments · May be fixed by #12094
Assignees

Comments

@protolambda
Copy link
Contributor

The op-node must feed into the op-supervisor, the op-supervisor does not rely on the EL for state.
The op-supervisor was pulling safe and finalized from the EL
(this originated from prototype code), intending to retrieve local-safe, but it was the cross-safe.
Creating a cyclic dependency, keeping cross-safe stuck at genesis.

To fix this, we need to modify the op-node/rollup/interop deriver to emit RPC updates to the op-supervisor when local-safe data changes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: In progress
Development

Successfully merging a pull request may close this issue.

1 participant