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

TBD: Looser coupling between L2 blocks and L1 origin #316

Open
alfonso-op opened this issue Aug 6, 2024 · 2 comments
Open

TBD: Looser coupling between L2 blocks and L1 origin #316

alfonso-op opened this issue Aug 6, 2024 · 2 comments
Assignees

Comments

@alfonso-op
Copy link

Amend chain derivation rules such that not every L1 block needs to serve as a unique origin for L2 blocks. Instead, the L1 origin should be able to represent a range of L1 blocks, allowing L2 block times to be better decoupled from the L1

This capability may best be built leveraging the proposed deposit queue (see spec).

Additional context in this discussion thread.

Note: this is not a must for Holocene, hence P2 priority. We could try to at least implement and include the deposit queue in Holocene so we can target the L2/L1 decoupling in the subsequent hard fork.

@BlocksOnAChain
Copy link
Contributor

We might want to consider if this should be a P1, based on internal chats we had during planning. @sebastianst @roberto-bayardo - let's discuss it on the Kick-off call.

@sebastianst
Copy link
Member

This will surely not make it into Holocene, changing accordingly.

@sebastianst sebastianst changed the title Holocene: Looser coupling between L2 blocks and L1 origin TBD: Looser coupling between L2 blocks and L1 origin Sep 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Todo
Development

No branches or pull requests

4 participants