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.

Sign up for GitHub

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

Jump to bottom

Interop: integrate cross-unsafe safety progression into driver. #10884

Closed
Tracked by #10896
protolambda opened this issue Apr 1, 2024 · 1 comment
Closed
Tracked by #10896

Interop: integrate cross-unsafe safety progression into driver. #10884

protolambda opened this issue Apr 1, 2024 · 1 comment
Assignees
@protolambda
Milestone
Interop: Stable D...

Comments

@protolambda
Copy link
Contributor

This depends on the refactor changes of #10888.
Once refactored, we can add the new cross-unsafe label as introduced by the interop verifier specs.
This requires additional conditional(s)/effect(s) to be added to the driver to pick up on the safety changes.
@protolambda protolambda self-assigned this Apr 1, 2024
@hamdiallam hamdiallam mentioned this issue Jun 17, 2024
Closed
26 tasks
@tynes tynes transferred this issue from another repository Jun 17, 2024
@tynes tynes transferred this issue from ethereum-optimism/temp-export Jun 17, 2024
@tynes tynes added this to the Interop: Devnet 1 milestone Jun 17, 2024
@protolambda
Copy link
Contributor Author

This was implemented already, closing

@github-project-automation github-project-automation bot moved this from Backlog to Done in Interoperability Nov 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@protolambda protolambda

Labels
None yet
Projects
Interoperability
Status: Done
Milestone
Interop: Stable Devnet
Development

No branches or pull requests
2 participants
@tynes @protolambda