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 Mar 5, 2025. It is now read-only.
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?
account.signTransaction({to: ENV.contract_address,data: data,gas: '80000',chainId: 1},function(err,res){web3.eth.sendSignedTransaction(res.rawTransaction,function(sendErr,sendRes){// When the account used to sign is known to the provider it works// When the account used to sign is not known it raises the error});});
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:
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: