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

Historical EIP-1186 eth_getProof support for op-stack Withdrawal proofs #8147

Open
0xOsiris opened this issue May 7, 2024 · 2 comments
Open
Labels
A-rpc Related to the RPC implementation C-enhancement New feature or request S-stale This issue/PR is stale and will close with no further activity

Comments

@0xOsiris
Copy link

0xOsiris commented May 7, 2024

Describe the feature

Currently Reth does not offer support for eth_getProof on historical blocks. This breaks compatibility with the op-stack having Reth running as the sequencing execution client as Reth will not be able to generate withdrawal proofs for the proposer to post to L1 (except at the tip).

Additional context

Ref: https://github.com/ethereum-optimism/optimism/blob/89a3a5f32b79b2447690cdac70b1df498ffdb25c/op-node/withdrawals/utils.go#L102

Related to: #5246

@0xOsiris 0xOsiris added C-enhancement New feature or request S-needs-triage This issue needs to be labelled labels May 7, 2024
@shekhirin shekhirin added A-rpc Related to the RPC implementation and removed S-needs-triage This issue needs to be labelled labels May 8, 2024
@0xKitsune
Copy link
Contributor

Just a quick update, @0xOsiris and I have started working on this. I will open a draft PR with a few questions a little later today.

Copy link
Contributor

This issue is stale because it has been open for 21 days with no activity.

@github-actions github-actions bot added the S-stale This issue/PR is stale and will close with no further activity label May 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-rpc Related to the RPC implementation C-enhancement New feature or request S-stale This issue/PR is stale and will close with no further activity
Projects
Status: Todo
Development

No branches or pull requests

3 participants