Calling eth_signTransaction via JSON RPC reports "gas not specified" when gas field missing in transaction

[th4s]

According to the JSON RPC spec eth_signTransaction uses a gas default. However, when trying to sign a transaction with the gas field missing, geth reports { code: -32000, message: "gas not specified" }.

This does not happen when e.g. using the same transaction with the eth_sendTransaction procedure.

I am not sure if this is intended behavior or a bug. This behavior was observed using geth in --dev mode.

[MariusVanDerWijden]

Yeah you're right, some methods calculate meaningful default values for the gas, gasprice and other fields while others do not. We're currently looking into creating a new standard for JSON-RPC requests s.th. we can properly test against it and find issues like this. If it is okay for you, I would propose not to fix this bug right now but rather wait until the new specification is written.

[th4s]

Thanks for the info. I am currently writing an alternative web3 implementation and noticed this one because I run some tests as integration tests against a geth node in --dev mode. There are some other deviations from the spec. Is there any interest to collect these deviations at some place?

From my side there is no need to fix this and we can wait for the new spec :)

[MariusVanDerWijden]

Yes, we collect these deviations here: ethereum-oasis-op/eth1.x-JSON-RPC-API-standard#5
If you're interested in joining the calls about the JSON-RPC spec you can join the Ethereum R&D discord, there's a json-rpc-api channel there

[th4s]

Thanks for the link :) I will add my findings there. Also thanks for the discord link 👍