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

[Feature] Fill in Operator Fee Network Upgrade Transaction Bytecodes #428

Open
refcell opened this issue Feb 11, 2025 · 0 comments · May be fixed by #411
Open

[Feature] Fill in Operator Fee Network Upgrade Transaction Bytecodes #428

refcell opened this issue Feb 11, 2025 · 0 comments · May be fixed by #411
Assignees
Labels
A-consensus Area: consensus crate C-blocked Category: This cannot move forward until something else changes H-isthmus Hardfork: required for Isthmus hardfork

Comments

@refcell
Copy link
Collaborator

refcell commented Feb 11, 2025

Component

consensus

Describe the feature you would like

The operator fee is specified to be part of the isthmus hardfork.

As part of the Isthmus hardfork, the isthmus activation block contains these network upgrade transactions.

These are implemented in op_alloy_consensus in this draft PR.
op-alloy-consensus reads in the bytecode for the following deployed contracts.

  • Gas Price Oracle
  • L1 Block
  • Operator Fee Vault
  • EIP-2935 Predeploy

Notice, as mentioned in the pr comments, the contract bytecode is missing for:

  • Gas Price Oracle
  • L1 Block
  • Operator Fee Vault

These cannot be filled in until the Operator Fee contract implementation is merged in the Optimism Monorepo and a release is cut that produces the contract creation bytecode that can be filled in here. Effectively, this means ethereum-optimism/optimism#12166 has to be merged and a contract release cut to produce the bytecode for these contracts.

Additional context

No response

@refcell refcell added A-consensus Area: consensus crate C-blocked Category: This cannot move forward until something else changes H-isthmus Hardfork: required for Isthmus hardfork labels Feb 11, 2025
@refcell refcell self-assigned this Feb 11, 2025
@refcell refcell linked a pull request Feb 11, 2025 that will close this issue
@refcell refcell moved this from Backlog to TODO in Project Tracking 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 crate C-blocked Category: This cannot move forward until something else changes H-isthmus Hardfork: required for Isthmus hardfork
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant