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: persist index of cross-safe and local-safe increments per L1 block #12076

Closed
protolambda opened this issue Sep 24, 2024 · 0 comments · Fixed by #12436
Closed

Interop: persist index of cross-safe and local-safe increments per L1 block #12076

protolambda opened this issue Sep 24, 2024 · 0 comments · Fixed by #12436
Assignees

Comments

@protolambda
Copy link
Contributor

cross-safe accuracy depends on reasoning what L2 block is derived from what L1 block.
This information is not registered onchain, as it can only be reasoned about after posting the batch that confirms the data.
Consistency and completeness of this offchain data is challenging.

To serve the data needed to limit cross-validation to a particular L1 view (see #12075 ) we need to maintain a mapping of what L2 block was derived from what L1 block.
There is a design-doc covering this here.

We do not need the reorg support with Devnet 1, but do want to maintain a minimal index of the required safety information to provide accurate cross-safe and finalized L2 block information to the user.

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

Successfully merging a pull request may close this issue.

2 participants