Facing SERVER_ERROR which calling contract function

[shivam0x]

Hi @ricmoo I'm facing this issue with a particular contract. The same code for the same other contracts(generated by the same factory) is working fine. Not able to figure out what the issue is. Any help here?

{"reason":"bad result from backend","code":"SERVER_ERROR","method":"estimateGas","params":{"transaction":{"from":"0x0CbC4E5E965feC28D934e2Cafb7Df50369241215","to":"0xEA017BfB09aD1C295C6E18CE22A41A3B7A826Aab","data":"0x6c31364c000000000000000000000000000000000000000000000000000001797b9f949e0000000000000000000000009506d37f70eb4c3d79c398d326c871abbf10521d00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000064"}},"error":{"reason":"invalid BigNumber value","code":"INVALID_ARGUMENT","argument":"value"}}

[zemse]

Hey I see "error":{"reason":"invalid BigNumber value","code":"INVALID_ARGUMENT","argument":"value" from the server which seems like an ethers js error, can you include some code snippet or what backend you're using?

[shivam0x]

This is the code snippet where I'm facing the issue.

As its a write transaction so I'm using metamask provider in this case else for reading I'm using alchemy.

[zemse]

As far I'm understanding this, first eth_estimateGas is called to estimate a gasLimit value. But the response from your backend Metamask for this rpc call is an invalid value (it should be something like number or hex string representation of number). You should be able to prevent this by manually passing in a gasLimit override.

Now metamask should give you a value here. I have never encountered such edge case. I want to see the response of this from metamask. Can you do the following and share the result:

try {
const result = await provider.send('eth_estimateGas', [{
"from":"0x0CbC4E5E965feC28D934e2Cafb7Df50369241215",
"to":"0xEA017BfB09aD1C295C6E18CE22A41A3B7A826Aab",
"data":"0x6c31364c000000000000000000000000000000000000000000000000000001797b9f949e0000000000000000000000009506d37f70eb4c3d79c398d326c871abbf10521d00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000064"
}])
console.log('success', result)
} catch (e) {
console.log('err', e);
}

Edit I just tried it on mainnet: I get execution reverted: SafeERC20: low-level call failed. Seems like a require statement failing. I am not able to reproduce the error you're getting in the OP. Do you still get the same error?

[shivam0x]

@zemse thanks for your reply. Yes, it should revert in your case as this is onlyOwner function.

I'll give the above solution is try but I think by this time the client might have used a manual process by now.
Not sure when I'll be able to reproduce this. Also any other thing which I can try in this case as this is the first time I'm facing this issue that too only for 1 product, for all the other products(same code) for the same factory its working fine.

[shivam0x]

Again faced similar issue with another use:

[zemse]

The json rpc resonse body contains message: execution reverted. Also given that you're getting this occasionally, are you doing some complex stuff in the call?

• Working out a decision tree of stuff happening inside might help you guess the code failing.
• Also tenderly has a option to simulate calls, if you have verified contracts on etherscan it will show you even the line on solidity code that is failing.

Lmk if you solve it or need help with it

[shivam0x]

The above problem I fixed with some workaround from my frontend but still stuck with this problem. Haven't got any solution for this.

[Nikhil1419]

Hi @ShivamDev31
Any solution on this?

[shivam0x]

Hi, @Nikhil1419 didnt face the same issue again but I'm facing another SERVER_ERROR issue
@zemse @ricmoo a lot of users are facing this issue on ethers v5.4.4. Have already gone through #1766 and migrating to getDefaultProvider("homested") for time being instead of alchemy rpc provider.

Another observation is that chrome users(limited users not all and we are not able to reproduce this) are facing this issue and it's working fine on brave.

[ricmoo]

Closing older issues. But if this is still happening in v6, please re-open or start a new issue.

Thanks! :)