You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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).
The text was updated successfully, but these errors were encountered:
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).
The text was updated successfully, but these errors were encountered: