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: op-supervisor start at interop upgrade #13732

Open
protolambda opened this issue Jan 13, 2025 · 0 comments
Open

Interop: op-supervisor start at interop upgrade #13732

protolambda opened this issue Jan 13, 2025 · 0 comments
Assignees
@tyler-smith @axelKingsley
Labels
A-op-supervisor Area: op-supervisor H-interop Hardfork: change planned for interop upgrade
Milestone
Interop: Stable D...

Comments

@protolambda
Copy link
Contributor

The op-supervisor executing-message checks need to respect the interop start boundary.
Chains that migrate to interop need to be indexed starting from the hardfork.
And effectively make their anchor-point the interop-start, or apply additional boundary checks on the DB to enforce the starting point.
@protolambda protolambda added the A-op-supervisor Area: op-supervisor label Jan 13, 2025
@protolambda protolambda added this to the Interop: Stable Devnet milestone Jan 13, 2025
@protolambda protolambda mentioned this issue Jan 13, 2025
Closed
@protolambda protolambda added the H-interop Hardfork: change planned for interop upgrade label Jan 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@tyler-smith tyler-smith

@axelKingsley axelKingsley

Labels
A-op-supervisor Area: op-supervisor H-interop Hardfork: change planned for interop upgrade
Projects
Interoperability
Status: No status
Milestone
Interop: Stable Devnet
Development

No branches or pull requests
3 participants
@tyler-smith @axelKingsley @protolambda