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

Investigate anchoring L1 state on L2 #530

Open
2 of 6 tasks
kyzooghost opened this issue Jan 10, 2025 · 0 comments
Open
2 of 6 tasks

Investigate anchoring L1 state on L2 #530

kyzooghost opened this issue Jan 10, 2025 · 0 comments
Assignees
@kyzooghost
Labels
C: Contracts Contracts Smart Contract related P2: Medium Issue priority: medium

Comments

@kyzooghost
Copy link
Contributor

kyzooghost commented Jan 10, 2025 •
edited by thedarkjester
Loading

Description

Investigate anchoring L1 state on L2

Motivation

By enabling L1 state on L2, it will be possible to validate L1 data for consumption on L2 via means such as CCIP Gateway and storage proofs.

Tasks

  • Document the solution space for investigating L1 state on L2, including pros, cons/risks and time estimates

Acceptance criteria

  • Document complete and discussion on next action steps

Risks

  • Missed complexity
  • Take too much time for investigation - many approaches out in the wild touching on this topic

Remember to

  • Add the documentation label in case there is an impact on the documentation
  • Add priority and team labels
@kyzooghost kyzooghost added C: Contracts Contracts Smart Contract related P2: Medium Issue priority: medium labels Jan 10, 2025
@kyzooghost kyzooghost changed the title Copy of Investigate adding a rollup soundness alert Investigate anchoring L1 state on L2 Jan 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@kyzooghost kyzooghost

Labels
C: Contracts Contracts Smart Contract related P2: Medium Issue priority: medium
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@thedarkjester @kyzooghost