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

EIP1186AccountProofResponse verification against state root #8175

Closed
puma314 opened this issue May 9, 2024 · 1 comment · Fixed by #8220
Closed

EIP1186AccountProofResponse verification against state root #8175

puma314 opened this issue May 9, 2024 · 1 comment · Fixed by #8220
Assignees
Labels
A-trie Related to Merkle Patricia Trie implementation C-enhancement New feature or request

Comments

@puma314
Copy link

puma314 commented May 9, 2024

Describe the feature

Right now Reth has no good functions or libraries for merkle proof verification. Merkle proof verification against the state root is important for both fault proofs and zkEVMs, to verify that accounts and storage slots against a state root of a particular block, before processing a batch of transactions.

In particular, it would be great to implement a method like this one from the optimism codebase in golang as a primitive in Reth or some other appropriate library (alloy or something else).

Additional context

No response

@puma314 puma314 added C-enhancement New feature or request S-needs-triage This issue needs to be labelled labels May 9, 2024
@puma314
Copy link
Author

puma314 commented May 9, 2024

Slightly related to #8147, cc @0xKitsune @0xOsiris

@rkrasiuk rkrasiuk added A-trie Related to Merkle Patricia Trie implementation and removed S-needs-triage This issue needs to be labelled labels May 9, 2024
@rkrasiuk rkrasiuk self-assigned this May 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-trie Related to Merkle Patricia Trie implementation C-enhancement New feature or request
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

2 participants