feat(proxyd): add consensus rewrite support for eth_getBlockReceipts #17
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.
Summary
This PR adds consensus rewrite support for the
eth_getBlockReceiptsmethod in proxyd, enabling it to participate in the consensus-aware request rewriting system.Changes
eth_getBlockReceiptsto rewrite method list: The method is now included in the consensus rewrite logic alongsidedebug_getRawReceiptsandconsensus_getReceiptseth_getBlockReceiptsto the list of rewritten request methods in README.mdNewMetricsClientfunction call inotel_test.goby adding missing parameterseth_getBlockReceiptsmethod testingTechnical Details
The
eth_getBlockReceiptsmethod is now handled by therewriteParamfunction with the following configuration:This ensures that when clients request block receipts using consensus tags (
latest,safe,finalized), proxyd will rewrite the request to use the resolved consensus block number before forwarding to backends.Testing
eth_getBlockReceiptsmethodImpact
This change improves the consistency of block receipt responses when using consensus-aware backend groups, ensuring clients receive receipts from the same consensus block across different backend services.