-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
op-node: op-node interop block verification (devnet-1 scope) #11611
Conversation
I cut a new PR on top of my API to address this. |
c17346d
to
6934085
Compare
Opened #11672 to track the finalizer changes to make in op-node, in devnet 2 scope. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No blocking comments
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
Unrelated contracts test flakes. Going to rebase, so CI can run against latest develop cleanly. |
…ver step, to poll for supervisor safety changes
dad07e6
to
d9c22e4
Compare
…m-optimism#11611) * op-node: experimental interop block verification * op-node: supervisor RPC init * op-e2e/actions: test interop safety checks * op-e2e/op-node: test fixes * op-node: update comments * op-node: unit-test interop deriver, trigger cross-safe updates on driver step, to poll for supervisor safety changes * op-node: add more comments, fix flag description * op-e2e: fix rebase, add missing argument
Description
Op-node changes needed to interface with the new op-supervisor service for cross-L2 safety checks of L2 blocks.
TODO:
invalid
safety status (or something akin to that) to supervisor types/API, to identify blocks with invalid executing messages.Tests
Metadata
Fix #11312
Also fix #10886