Inconsistency in eth_sendTransaction input vs data
shanejonas opened this issue · comments
The eth_sendTransaction method in this spec currently lists the input parameter as a valid key, however, the actual API uses data as the key for this parameter. This can cause confusion for developers using the specification and implementing the method. Additionally, the data parameter is correctly used as the return type for eth_getBlockByHash and other block read methods, but its usage in eth_sendTransaction is wrong.
To address this issue, it is suggested that the eth_sendTransaction method be removed in the OpenRPC specification and instead, have a wallet-specific OpenRPC specification.
This issue is related to #363.
input is the correct one.