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: substitute finalizer deriver component with supervisor backend #11672

Closed
protolambda opened this issue Aug 29, 2024 · 1 comment
Closed
Assignees

Comments

@protolambda
Copy link
Contributor

With interop devnet v1, the safe signal is currently assumed to be cross-safe still upon processing in the op-node finalizer component, and thus fine to promote to cross-finalized.

In later interop iterations we want to substitute the finalizer for L2-finality determination by the op-supervisor.

See ethereum-optimism/design-docs#70 for context on how the op-supervisor backend can maintain finality data.

The module that then maintains the safety-index can be embedded into the op-node, for non-interop chains to not run an op-supervisor service, while still doing local interop (historical events proving) and potential one-way interop with L1 (pulling events from L1 like you would from L2).

@protolambda
Copy link
Contributor Author

Duplicate of #12357

@protolambda protolambda marked this as a duplicate of #12357 Oct 28, 2024
@protolambda protolambda closed this as not planned Won't fix, can't repro, duplicate, stale Oct 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

No branches or pull requests

1 participant