feat: Pureth in Reth - #26881
Draft
ArshLabs wants to merge 30 commits into
Draft
feat: Pureth in Reth#26881ArshLabs wants to merge 30 commits into
ArshLabs wants to merge 30 commits into
Conversation
feat: add progressive withdrawal roots
feat(pureth): add receipt query and proof primitives
fix(pureth): validate receipt bounds from proofs
feat(pureth): add typed receipt representations
feat(pureth): resolve paths against typed receipts
feat(pureth): retain receipt trees for proofs
feat(pureth): add receipt proof access
feat(pureth): add deterministic receipt provider
feat(pureth): add receipt query service and RPC
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Draft PR for the Pureth implementation in Reth
current changes:
pureth_queryRPC over the deterministic receipt provider (#10)the receipt side currently uses an EIP-6466 informed project v0 (not exact EIP-6466 support yet)
tracking issue: #26880