Error 500: missing revert data in call exception

[jasper_dcip]

We’re using Snapshot, which uses an archive node from Moralis, which is returning 500 errors without much debugging information. I found this other topic with the exact same error, which might be related:

Read-only gas limit is too low probably

I am using Snapshot (https://snapshot.org/) which uses Moralis. Recently one of our Quickswap proposals wasn’t working on Snapshot. We traced the issue down to this Moralis node RPC error: “missing revert data in call exception”. [image] We suspect this is caused by a read-only gas limit on the node. Assuming that we were able to do a work around to get our proposal working but it is not a good workaround and may break in the future. It is possible that the read-only gas limit on the Mora…

{
  "jsonrpc": "2.0",
  "error": {
    "code": 500,
    "data": {
      "reason": "missing revert data in call exception",
      "code": "CALL_EXCEPTION",
      "error": {
        "reason": "processing response error",
        "code": "SERVER_ERROR",
        "body": "{\"jsonrpc\":\"2.0\",\"id\":170,\"error\":{\"code\":-32000,\"message\":\"header not found\"}}\n",
        "error": {
          "code": -32000
        },
        "requestBody": "{\"method\":\"eth_call\",\"params\":[{\"to\":\"0x1ee38d535d541c55c9dae27b12edf090c608e6fb\",\"data\":\"0x252dba42000000000000000000000000000000000000000000000000000000000000002000000000000000000000000000000000000000000000000000000000000000010000000000000000000000000000000000000000000000000000000000000020000000000000000000000000308fc5cdd559be5cb62b08a26a4699bbef4a888f0000000000000000000000000000000000000000000000000000000000000040000000000000000000000000000000000000000000000000000000000000002470a082310000000000000000000000001d780836c42875e65cce986485d2ccde5f89ee5f00000000000000000000000000000000000000000000000000000000\"},\"0xc27678\"],\"id\":170,\"jsonrpc\":\"2.0\"}",
        "requestMethod": "POST",
        "url": "https://speedy-nodes-nyc.moralis.io/b9aed21e7bb7bdeb35972c9a/bsc/mainnet/archive"
      },
      "data": "0x"
    }
  }
}

The archive node Snapshot is using is: https://speedy-nodes-nyc.moralis.io/b9aed21e7bb7bdeb35972c9a/bsc/mainnet/archive . Is there something we or Snapshot might do to resolve this, based on the information provided above or is it a “Moralis issue”?