You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jun 3, 2022. It is now read-only.
The naming for the RPC call eth_sendRawTransaction is misleading as this call allows to send a signed transaction. The term raw is used in the context of transactions for unsigned data (raw transaction hash). Changing the RPC name to eth_sendSignedTransaction would make the usage more clear and prevent misuse.
The text was updated successfully, but these errors were encountered:
Georgi87
changed the title
Rename eth_sendRawTransaction to eth_sendSignedTransaction
Rename sendRawTransaction to sendSignedTransaction
Jan 27, 2017
frozeman
changed the title
Rename sendRawTransaction to sendSignedTransaction
Rename eth_sendRawTransaction to eth_sendSignedTransaction
Jan 27, 2017
I fully support this and in web3.js 1.0 it will be already called eth.sendSignedTransaction() @bas-vk@obscuren can we change that and deprecate the old name?
The name was initially given by @SilentCicero who just came up with the name and i didn't had much time to think about a better one back then.
Good to see parity also sees this as an issue. I think the difference between submitTransaction and sendTransaction is not really obvious with this naming but it is much better than sendRawTransaction.
The naming for the RPC call
eth_sendRawTransaction
is misleading as this call allows to send a signed transaction. The termraw
is used in the context of transactions for unsigned data (raw transaction hash). Changing the RPC name toeth_sendSignedTransaction
would make the usage more clear and prevent misuse.The text was updated successfully, but these errors were encountered: