-
-
Notifications
You must be signed in to change notification settings - Fork 1.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
Every transaction failing with JsonRPCSigner #365
Comments
Can you provide the contract method? It looks like a |
It also looks like it is using 90k gas... is that sufficient? Can you run: let tx = {
to: "0x0dc5f8a12c0af9dda2fd7f76823e4b3ba6f8bc1e",
data: "0x93767f3200000000000000000000000000000000000000000000000000000000000001000000000000000000000000000000000000000000000000000000000000000140000000000000000000000000898db302944455dbc6ad7f58452c74e26400eb67000000000000000000000000f4d5edec750a6736817a548742a1a8db36de4f0000000000000000000000000000000000000000000000000000000000000001a000000000000000000000000000000000000000000000152d02c7e14af6800000000000000000000000000000000000000000000000000000000000000133f021000000000000000000000000000000000000000000000000000000000000000a000000000000000000000000000000000000000000000000000000000000000b746f6b6930303132333131000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000002430623966366161332d633463372d346636342d626632642d3039326330343936653935350000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000035553440000000000000000000000000000000000000000000000000000000000"
};
provider.estimateGas(tx).then((gasLimit) => {
console.log(gasLimit);
}); The only thing that should have changed is I let the node compute its expected gas, rather than perform the estimate separately. Also, what node is this? Parity, Ganache, Geth? |
createToki method in this contract. And it is a geth node. |
Can you also look up older transactions, which worked, and see what gasLimit was set? |
Looks like 90k is the default: https://github.com/ethereum/wiki/wiki/JSON-RPC#eth_sendtransaction My guess is that when it was using estimateGas directly, it was determining a much higher gas limit. I can go back to automatically filling in the gas limit. I need to think for a few minutes what the "right" (least wrong?) thing is to do... |
I think that what is happening. The successful transaction gas used was 2113100 wei. And the gas limit on the network is 8000000. |
I was able to make successful transactions after passing the options for transaction with higher gas limit. |
Ok... I will add gas estimation back in. I think it is easier for people to hard-code 90k if that is what they want, but it is far more useful of a default to pick a sane gas limit. :) |
Sounds good. :) |
This should be fixed now. Give it a go? |
That worked. Thanks @ricmoo . :)
👍 |
After the last night change for bulk transactions,
every transaction using JsonRpcSigner is failing with below error.
The text was updated successfully, but these errors were encountered: