JsonRpcProvider error propagation

[enjoooyer]

I have two rpcs created

const rpc1 = new JsonRpcProvider(rpcUrl, chainId, { staticNetwork: Network.from(chainId) })
const rpc2 = new JsonRpcProvider(rpcUrl, chainId)

const a = await rpc1.getBlockNumber()
const b = await rpc2.getBlockNumber()

rpc1 does not raise rate limiting error, instead stays hanging on the promise til it times out.

rpc2 does propagate rate limiting errors fine.

error (error={ "code": -32007, "message": "1/second request limit reached - reduce calls per second or upgrade your account at quicknode.com" }, payload={ "id": 5, "jsonrpc": "2.0", "method": "eth_chainId", "params": [  ] }, code=UNKNOWN_ERROR, version=6.12.1)

It's good to use staticNetwork to avoid unnecessary chain id calls, but how to propagate the error also?

[ricmoo]

Yes, you should absolutely use staticNetwork if it is safe to do so (i.e. you know the network cannot change), but you can also specify staticNetwork: true to simplify your life a bit.

What do you mean by propagate the error?

[enjoooyer]

I have an rpc url that I've purposfully rate limited to 1req/s and 10req/min in order to test how it behaves.

So when I run this code

const rpc1 = new JsonRpcProvider(rpcUrl, chainId, { staticNetwork: Network.from(chainId) })
while (true) {
  const balance = await rpc1.getBalance(ZERO_ADDRESS)
  console.log(new Date(), balance)
}

output is

2024-08-21T05:14:03.253Z 66758556173721559073n
2024-08-21T05:14:18.153Z 66758556173721559073n
2024-08-21T05:14:35.849Z 66758556173721559073n
2024-08-21T05:14:51.198Z 66758556173721559073n

see how slowly it fetches the balance. This await rpc1.getBalance(ZERO_ADDRESS) stays pending til the RPC rate limit expires.

Now same code, but without staticNetwork.

const rpc2 = new JsonRpcProvider(rpcUrl, chainId)
while (true) {
  const balance = await rpc2.getBalance(ZERO_ADDRESS)
  console.log(new Date(), balance)
}

it immediately errors with

{
  "_id": "FiberFailure",
  "cause": {
    "_id": "Cause",
    "_tag": "Fail",
    "failure": {
      "cause": {
        "code": "UNKNOWN_ERROR",
        "error": {
          "code": -32007,
          "message": "1/second request limit reached - reduce calls per second or upgrade your account at quicknode.com"
        },
        "payload": {
          "method": "eth_getBalance",
          "params": [
            "0x0000000000000000000000000000000000000000",
            "latest"
          ],
          "id": 2,
          "jsonrpc": "2.0"
        },
        "shortMessage": "could not coalesce error"
      },
      "_tag": "UnknownException",
      "error": {
        "code": "UNKNOWN_ERROR",
        "error": {
          "code": -32007,
          "message": "1/second request limit reached - reduce calls per second or upgrade your account at quicknode.com"
        },
        "payload": {
          "method": "eth_getBalance",
          "params": [
            "0x0000000000000000000000000000000000000000",
            "latest"
          ],
          "id": 2,
          "jsonrpc": "2.0"
        },
        "shortMessage": "could not coalesce error"
      }
    }
  }
}

which is expected behaviour and one that I want to achieve with staticNetwork.

So question is how to configure new JsonRpcProvider(rpcUrl, chainId, { staticNetwork: Network.from(chainId) }) to propagate 429 errors instead of hanging on the pending promise til it resolves / times out.