Add difficulty to JSON-RPC blocks #2082
Merged
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.
Description
For compatibilty with ethers 6, which fails with
Error: invalid value for value.difficulty
, otherwise.Tested
The regression test is included in #2081. This PR is provided separately, in case the other PR takes long to merge due to a potentially required node version update for recent ethers versions (node>=14).
Related issues
Backwards compatibility
Adding a field to the JSON object should be harmless for reasonably implemented users. I also don't know a way to fix the problem in an even safer way.