Stage 1: Collect - inconsistencies

[tkstanczak]

Please provide a list of inconsistencies between JSON RPC providers that are known to you.

[tkstanczak]

error messages and error codes

[tkstanczak]

eth_estimateGas, eth_call and similar behaviour when the 'from' field is left empty
eth_estimateGas, eth_call and similar behaviour when the 'gas' field is left empty

[tkstanczak]

timeouts

[tkstanczak]

Differences in handling revert messages when executing eth_call

[MariusVanDerWijden]

Default values for parameters: The eth_sendTransaction spec here: https://eth.wiki/json-rpc/API#eth_signtransaction proposes a default value of 90.000 for gas. Geth currently just errors if no gas value is provided while we (in similar methods) execute an EstimateGas call to properly estimate the gas usage.

[th4s]

Differences between https://eth.wiki/json-rpc/API and geth (in --dev mode) I noticed:

1. Compiler related RPCs are not supported (I think this is well known, but just for completeness). This includes:

• eth_getCompilers
• eth_compileSerpent
• eth_compileSolidity
• eth_compileLLL

2. Same for the mining RPCs

• eth_getWork
• eth_submitWork
• eth_submitHashrate

3. The complete db_... and shh_... (whisper has been moved out of geth I think) namespaces do not exist.

4. eth_signTransaction should return the hex-encoded transaction, but geth returns
   {"raw": hex_encoded_tx, "tx": json_encoded_tx}.

5. Using eth_getFilterLogs with a filter_id returned by eth_newBlockFilter does not seem to work. Geth returns { code: -32000, message: "filter not found" }. However, doing this with eth_getFilterChanges works. I am not sure if this is intended or a bug.

[tkstanczak]

Within:

• eth_call
• parity_call
• eth_estimateGas

There are multiple inconsistencies in what we use when:

• From field is empty
• Gas field is empty
• GasPrice is empty

[tkstanczak]

debug_trace methods sometimes generate huge outputs -> multiple gigabytes of data.
We could clarify the limits / timeouts and client behaviours when handling such requests.

[tkstanczak]

Http/2 support

[tkstanczak]

Pending block parameter behaviour

[rain-on]

Quorum's admin_peers Json RPC (appears to) return its peer's Ethereum Address in the "id" field, rather than the peer's Public Key (as indicated by documentation).
Besu supplies the Public key.