fix: filter out Nethermind-specific error field from receipt comparisons#17
Merged
fix: filter out Nethermind-specific error field from receipt comparisons#17
Conversation
Nethermind includes a non-standard 'error' field on reverted transaction receipts which is not part of the Ethereum JSON-RPC spec. This caused false failures when comparing get_block_receipts responses between Reth and Nethermind. This change recursively filters out client-specific extension fields before comparing RPC responses.
ac3df75 to
cb0e815
Compare
joshieDo
approved these changes
Jan 13, 2026
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.
Summary
Nethermind includes a non-standard
errorfield on reverted transaction receipts which is not part of the Ethereum JSON-RPC spec. This caused false failures when comparingget_block_receiptsresponses between Reth and Nethermind.Changes
IGNORED_FIELDSconstant for client-specific extension fieldsfilter_ignored_fields()function that recursively removes these fields before comparisonExample
Nethermind returns:
{ "status": "0x0", "error": "revert", // <-- Nethermind-only, not in spec ... }Reth/Geth return:
{ "status": "0x0", ... }Testing
Tested locally against: