rpcdaemon: update JSON-RPC spec to fork 0502b44 #2113
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.
Recently, we cloned official Ethereum JSON-RPC Execution API repository into our fork in order to:
debug
,trace
,ots
)This PR updates our copy of the full specification to the version generated from erigontech/execution-apis@0502b44, which is equivalent to the official erigontech/execution-apis@3ae3d29 plus the following changes:
eth_getStorageAt
Fix eth_getStorageAt and uint256 definitions ethereum/execution-apis#509engine_forkchoiceUpdated
, which we previously applied directly to the generated our copy of the full spec rpcdaemon: fix Engine API V3 in JSON-RPC spec #1924Next Step
The next step will be a fully automated solution including our fork as Silkworm submodule (branch
main_silkworm
) and thus generating the full specification at build time.Extras
null
validation in ourjson_rpc::JsonRpcValidator
conan.cmake