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

[Tracking] Isthmus specs #516

Open
emhane opened this issue Jan 16, 2025 · 2 comments
Open

[Tracking] Isthmus specs #516

emhane opened this issue Jan 16, 2025 · 2 comments
Assignees
Labels
A-consensus Area: consensus layer A-evm Area: EVM A-execution Area: execution layer A-prover A: fault prover H-isthmus Hardfork: change is planned for Isthmus upgrade M-tracking Meta: tracking issue U-node Upgrade: involving changes to node component (cl, el, etc.)

Comments

@emhane
Copy link
Member

emhane commented Jan 16, 2025

Tracking isthmus spec. The noop specs are automatically confirmed for inclusion in Isthmus hard fork, because they are needed in order not to break from L1 hardforking.

inherited from Pectra

@emhane emhane added H-isthmus Hardfork: change is planned for Isthmus upgrade M-tracking Meta: tracking issue labels Jan 16, 2025
@emhane emhane pinned this issue Jan 16, 2025
@emhane emhane added U-node Upgrade: involving changes to node component (cl, el, etc.) A-evm Area: EVM A-consensus Area: consensus layer A-execution Area: execution layer A-prover A: fault prover labels Jan 16, 2025
@tynes
Copy link
Contributor

tynes commented Jan 28, 2025

For the system contracts being introduced, can we make sure we specify how they end up in the L2 state? We previously did it via special deposit transactions and also have used state setting directly in the EL. We prefer to not do the irregular state transition with state setting if possible. cc @refcell @emhane @meyer9

@refcell
Copy link
Contributor

refcell commented Feb 5, 2025

For the system contracts being introduced, can we make sure we specify how they end up in the L2 state? We previously did it via special deposit transactions and also have used state setting directly in the EL. We prefer to not do the irregular state transition with state setting if possible. cc @refcell @emhane @meyer9

I believe I did this here. Since the only one is EIP-2935. Both EIP-7002 and EIP-7251 predeploys are noted to not be included in isthmus.

@refcell refcell moved this to Backlog in Project Tracking Feb 10, 2025
@refcell refcell moved this from Backlog to In Progress in Project Tracking Feb 10, 2025
@refcell refcell self-assigned this Feb 11, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-consensus Area: consensus layer A-evm Area: EVM A-execution Area: execution layer A-prover A: fault prover H-isthmus Hardfork: change is planned for Isthmus upgrade M-tracking Meta: tracking issue U-node Upgrade: involving changes to node component (cl, el, etc.)
Projects
None yet
Development

No branches or pull requests

3 participants