EVM/Node: support [null] in [eth_call] fields

Valentin Chabocherequested to merge
vch9@evm-node-eth-call-null into master

What

Allows fields to be null in the JSON format

Why

It's an expected behavior for some RPCs. I noticed this while looking at geth documentation: https://www.quicknode.com/docs/ethereum/eth_call. I don't know how generalised this problem is.

How

Open the diff and look how beautiful this is.

Manually testing the MR

Run a local observer and do:

curl http://127.0.0.1:8545 \
  -X POST \
  -H "Content-Type: application/json" \
  --data '{"method":"eth_call","params":[{"from": null,"to":"0x6b175474e89094c44da98b954eedeac495271d0f","data":"0x70a082310000000000000000000000006E0d01A76C3Cf4288372a29124A26D4353EE51BE"}, "latest"],"id":1,"jsonrpc":"2.0"}'

Checklist

  • Document the interface of any function added or modified (see the coding guidelines)
  • Document any change to the user interface, including configuration parameters (see node configuration)
  • Provide automatic testing (see the testing guide).
  • For new features and bug fixes, add an item in the appropriate changelog (docs/protocols/alpha.rst for the protocol and the environment, CHANGES.rst at the root of the repository for everything else).
  • Select suitable reviewers using the Reviewers field below.
  • Select as Assignee the next person who should take action on that MR

Merge request reports