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-7685: General Purpose Execution Layer Requests #20

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

[Tracking] EIP-7685: General Purpose Execution Layer Requests #20

emhane opened this issue Jan 17, 2025 · 4 comments
Labels
A-op-alloy Area: op-alloy (op-rs dependency) A-op-geth Area: op-geth (go execution client incl. go evm) A-op-node Area: op-node (go consensus client) 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-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

Tracks spec inclusion and implementation of EIP-7685.

spec

rust

op-reth

kona

go

op-geth

op-node

  • <issue>

op-service
@emhane emhane added A-op-node Area: op-node (go consensus client) A-spec Area: spec H-pectra Hardfork: change planned for Pectra (L1) upgrade M-tracking Meta: tracking issue labels Jan 17, 2025
@emhane emhane mentioned this issue Jan 17, 2025
Open
@emhane emhane changed the title [Tracking] EIP-7685: General Purpose Execution Layer Requests [Tracking] EIP-7685: General Purpose Execution Layer Requests (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-7685: General Purpose Execution Layer Requests (noop) [Tracking] EIP-7685: General Purpose Execution Layer Requests Jan 17, 2025
@emhane emhane added H-isthmus Hardfork: change is planned for Isthmus upgrade A-op-alloy Area: op-alloy (op-rs dependency) A-op-reth Area: op-reth (rust execution client) A-op-geth Area: op-geth (go execution client incl. go evm) labels Jan 17, 2025
@emhane emhane mentioned this issue Jan 17, 2025
Closed
@emhane
Copy link
Member Author

emhane commented Jan 24, 2025

this one should also be pretty simple to close by eod or start next week @danyalprout @meyer9

@emhane
Copy link
Member Author

emhane commented Jan 27, 2025

is the go impl of this also finished? if so then we can close (yay!)

@meyer9
Copy link

meyer9 commented Jan 27, 2025

Just finished the go implementation here: ethereum-optimism/op-geth#478

Forgot about this change, but this is already implemented in Reth.

@emhane
Copy link
Member Author

emhane commented Jan 29, 2025

seems to me that op-node needs a smol fix too, checking that el doesn't send it any el requests, but not a blocker I believe. couldn't find an open or closed pr or issue that seems to address this in the optimism repo.

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-alloy Area: op-alloy (op-rs dependency) A-op-geth Area: op-geth (go execution client incl. go evm) A-op-node Area: op-node (go consensus client) 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-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