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

[Tracking] EIP-6110: Validator Deposits on Chain #21

Closed
emhane opened this issue Jan 17, 2025 · 4 comments
Closed

[Tracking] EIP-6110: Validator Deposits on Chain #21

emhane opened this issue Jan 17, 2025 · 4 comments
Labels
A-op-geth Area: op-geth (go execution client incl. go evm) A-op-reth Area: op-reth (rust execution client) A-spec Area: spec H-isthmus Hardfork: change is planned for Isthmus upgrade H-pectra Hardfork: change planned for Pectra (L1) upgrade M-platform M: platform development M-tracking Meta: tracking issue U-node Upgrade: involving changes to node component (cl, el, etc.) U-noop Upgrade: L1 feature not used on L2 requires action to disable

Comments

@emhane
Copy link
Member

emhane commented Jan 17, 2025 •
edited
Loading

spec

rust

op-reth

go

op-geth

  • <issue>
@emhane emhane added A-op-geth Area: op-geth (go execution client incl. go evm) A-op-reth Area: op-reth (rust execution client) A-spec Area: spec M-tracking Meta: tracking issue H-isthmus Hardfork: change is planned for Isthmus upgrade H-pectra Hardfork: change planned for Pectra (L1) upgrade labels Jan 17, 2025
@emhane emhane mentioned this issue Jan 17, 2025
Closed
@emhane emhane changed the title [Tracking] EIP-6110: Validator Deposits on Chain [Tracking] EIP-6110: Validator Deposits on Chain (noop) Jan 17, 2025
@emhane emhane added U-node Upgrade: involving changes to node component (cl, el, etc.) U-noop Upgrade: L1 feature not used on L2 requires action to disable labels Jan 17, 2025
@emhane emhane changed the title [Tracking] EIP-6110: Validator Deposits on Chain (noop) [Tracking] EIP-6110: Validator Deposits on Chain Jan 17, 2025
@emhane
Copy link
Member Author

emhane commented Jan 24, 2025

think this one also has a chance to be closed by eod, spec seems pretty straightforward @danyalprout @meyer9

@emhane emhane added the M-platform M: platform development label Jan 31, 2025
@emhane
Copy link
Member Author

emhane commented Jan 31, 2025

what's go side eta here @meyer9 ?

@meyer9
Copy link

meyer9 commented Feb 4, 2025

No need for network upgrade tx for this, but we should add a test to make sure nothing breaks when the contract is deployed. Opened a ticket here to track: ethereum-optimism/optimism#14155

@emhane
Copy link
Member Author

emhane commented Feb 6, 2025

ok nice, will close then since implementation is done to track incremental progress and link the issue for testing noop:ed predeploys to the root tracking issue.

@emhane emhane closed this as completed Feb 6, 2025
@emhane emhane mentioned this issue Feb 6, 2025
Closed
@refcell refcell moved this from Backlog to Done in Project Tracking Feb 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
A-op-geth Area: op-geth (go execution client incl. go evm) A-op-reth Area: op-reth (rust execution client) A-spec Area: spec H-isthmus Hardfork: change is planned for Isthmus upgrade H-pectra Hardfork: change planned for Pectra (L1) upgrade M-platform M: platform development M-tracking Meta: tracking issue U-node Upgrade: involving changes to node component (cl, el, etc.) U-noop Upgrade: L1 feature not used on L2 requires action to disable
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@meyer9 @emhane