-
Notifications
You must be signed in to change notification settings - Fork 5k
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
web3.eth.signTransactions has different result to eth.account.signTransaction #1125
Comments
Hm. i just send yesterday a transaction which i locally signed, which used sendSignedTransaction under the hood and it went through. Can you do some more tests manually? The result could be different as the signing changed, it might be that signTx on the geth node still returns the old signature type. If you test using the node and the tx goes through the signature is correct. |
You are right, Geth will send the transaction. I used the following test against a new dev instance of Geth so the nonce of
I'm closing as I only care that Geth will send transactions signed by web3.eth.account.signTransaction. I don't care that the hashes don't match. |
I can't get web3.eth.sendSignedTransaction to send locally signed transactions. I can successfully send transactions using web3.eth.sendTransaction, which signs the transaction on the remote node.
The first test in the below works which is using a connected geth 1.7.2 node to sign the transaction.
The second test fails which is signing the transaction locally using web3.eth.account.
The above tests are based off the example in the web3 1.0 documentation
http://web3js.readthedocs.io/en/1.0/web3-eth-accounts.html#id6
I was hoping the following PR in 1.0.0-beta.24 would fix the problem but it hasn't
#1111
The text was updated successfully, but these errors were encountered: