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 has been archived by the owner on Jan 21, 2022. It is now read-only.
If I call: this.web3.eth.sendSignedTransaction('0x' + serializedTx.toString('hex'))
I expect it to send the transaction.
Current Behavior
Instead I get the following internal json-rpc error: errors.js:29 Uncaught (in promise) Error: Returned error: {"id":4,"jsonrpc":"2.0","error":{"code":-32603}}
Possible Solution
I think sendSignedTransaction might not be supported, so adding support for it would be a solution
I was seeing the same behavior with ganache-cli due to this bug. I've submitted a PR to ethereumjs-tx. If that gets merged then the package will have to be updated in ganache-core.
@jasperdg Thanks for reporting! Please update to the latest Ganache. @ajhodges is correct that ethereumjs/ethereumjs-tx#113 is the culprit, but we worked around this in latest by rolling back to a prior version which didn't exhibit this issue.
Also please check your version numbers. Truffle's latest major version is 4.x.x.
When I try to use the sendSignedTransaction function according to the web3 documentation:
https://web3js.readthedocs.io/en/1.0/web3-eth.html#sendsignedtransaction
Expected Behavior
If I call:
this.web3.eth.sendSignedTransaction('0x' + serializedTx.toString('hex'))
I expect it to send the transaction.
Current Behavior
Instead I get the following internal json-rpc error:
errors.js:29 Uncaught (in promise) Error: Returned error: {"id":4,"jsonrpc":"2.0","error":{"code":-32603}}
Possible Solution
I think sendSignedTransaction might not be supported, so adding support for it would be a solution
Steps to Reproduce (for bugs)
https://ethereum.stackexchange.com/questions/48807/jsonrpc-error-on-sendsignedtransaction?noredirect=1#comment57826_48807
Your Environment
The text was updated successfully, but these errors were encountered: