This repository was archived by the owner on Mar 5, 2025. It is now read-only.
Accept predefined block numbers for eth_feeHistory #4213
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
Allow the
eth_feeHistorymethod to accept predefined block numbers, e.g. "latest". This is the appropriate schema type as defined in the ethereum spec: https://github.com/ethereum/eth1.0-specs/blob/master/json-rpc/spec.json.The current behavior of forcing the parameter into
utils.toHexactually does convert "latest" into a hex far beyond head resulting in the node response of "request beyond head block" (for geth).Type of change
Checklist:
npm run dtslintwith success and extended the tests and types if necessary.npm run test:unitwith success.npm run test:covand my test cases cover all the lines and branches of the added code.npm run buildand testeddist/web3.min.jsin a browser.CHANGELOG.mdfile in the root folder.