estimateGas call fails in optimism network.

[Kankan-0]

Description : estimateGas call fails if I try optimism rpc endpoints, with others it's successfully returning the result.

I'm using "ethers": "^5.5.3" version in my project, and while trying the following code I get the error: Error: gas required exceeds allowance

const ethers = require('ethers')
async function test() {
  let url
  url = 'https://kovan.optimism.io'
  // url = 'https://polygon-rpc.com'
  // url ="https://kovan.poa.network"
  // url = 'https://rinkeby.arbitrum.io/rpc'
  // url = 'https://mainnet.optimism.io'
  
  
  let provider=  new ethers.providers.JsonRpcProvider(url)
  const gasPrice =await provider.getGasPrice();
  const tx = {
    to: '0xb4DE0833771eae55040b698aF5eB06d59E142C82',     
    value: '0x1',
  }
  const estimatedGas = await provider.estimateGas(tx);
  
  console.log(gasPrice.toString())
  console.log(estimatedGas.toString())
}

test()

Here's the full error that I am getting.

All the other endpoints works fine except the optimism ones.
Can anyone suggest if I am doing something wrong?

Thanks.

[smartcontracts]

I think this is probably an issue with some quirk in the Optimism node and unlikely to be an Ethers issue.

[RobbingBlocks]

I think this is probably an issue with some quirk in the Optimism node and unlikely to be an Ethers issue.

I don't think so. I have actually noticed there being some issues in the Logging specifically around this method as well. It might be spread to other things too - haven't looked too deep yet. However I think ethers might have some pretty serious bugs in the logger when it comes to less common errors, and less common use cases.

For instance, I just discovered a way to crash my app by breaking something in the logger - meanwhile my entire implementation of ethers is wrapped in a try/catch to see if I can gracefully fail...

[zemse]

@Kankan-0 I just tried this example, and it seems to work.

ethers-repl> test()
Promise { <pending> }
10000
21000

Not really sure why it'd be failing when the issue was created, but since the transaction involves value: '0x1, and the node would consider Zero address by default as the caller when a from is not specified in estimateGas, hence the Zero address must possess at least 0x1 balance, which it now does.

[smartcontracts]

We (the Optimism team) did additional research and found that this was an issue over at QuickNode, the RPC provider behind both mainnet.optimism.io and kovan.optimism.io. QuickNode upgraded its infrastructure over the last few days and it seems that this problem has been fixed along with that upgrade. This can safely be closed as it's not an issue with ethers.js and it's also been fixed.

[Kankan-0]

Closing this issue since it's now fixed as per smartcontracts comment.