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

Implement op-geth's DA throttling in op-reth #13063

Open
alfonso-op opened this issue Nov 25, 2024 · 1 comment
Open

Implement op-geth's DA throttling in op-reth #13063

alfonso-op opened this issue Nov 25, 2024 · 1 comment

Comments

@alfonso-op
Copy link

A change was recently made to op-geth to enable DA throttling through a new RPC PR.

This feature should also be implemented in op-reth for parity to support chain operators who may want to run a mixture of op-geth and op-reth sequencers.

@alfonso-op alfonso-op added D-good-first-issue Difficulty: A great task to get started good first issue and removed D-good-first-issue Difficulty: A great task to get started labels Nov 25, 2024
@Dhir0808
Copy link

I'd like to work on implementing the DA throttling RPC functionality in op-reth. Here's my understanding and proposed approach:

  1. The implementation will mirror op-geth's recent RPC changes, adding two new methods:

    • eth_setDAGasPrice
    • eth_getDAGasPrice
  2. Key components to implement:

    • Add new RPC endpoints to the existing eth namespace
    • Implement DA throttling manager to handle gas price controls
    • Integrate with transaction pool management for throttling logic
    • Add appropriate tests for both RPC functionality and throttling behavior
  3. I'll ensure feature parity with op-geth to support chain operators running mixed op-geth/op-reth sequencers.

I have experience with Rust and implementing RPC endpoints. Would you like me to start with a draft PR focusing on the RPC interface first, or would you prefer a different approach?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

2 participants