-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
sendRawTransaction returns "Invalid JSON RPC Response" #1517
Labels
Bug
Addressing a bug
Comments
Got the same problem. Tried to upgrade web3 version to 1.0.0-beta.34 but it's still there. |
Same. It's probably related to #1793 — |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
I want to sign a raw transaction using an account which is not an account registered by the provider (I use Ganache), but when I send it using
web3.eth.sendRawTransaction
I get the following error message :However, when I send a raw transaction signed with an address which is an account listed in Ganache it works. Is it mandatory that the account used to sign the transaction is known to the provider?
Using Truffle Console (raw transaction signed by an account not listed in the provider)
Thanks for the help, I might have missed a point about providers and accounts.
Note that the error could be raised by the smart contract which uses a
require
, the point is that I have no issue when the account is one that the provider know.Web3 version : 0.20.4
The text was updated successfully, but these errors were encountered: