---
updatedAt: 2025-11-17T05:27:53.000Z
agentTools:
  projectIndex: https://docs.tatum.io/llms.txt
---

# Arbitrum -  Error: missing trie node

The Arbitrum chain went through a hard-fork from Classic to Nitro on August 31, 2022.

As a result of this, it is only possible to use `debug` methods from block 22.207.818 to the current one.

### List of impacted Arb Debug methods:

* [debug\_getbadblocks](https://docs.tatum.io/reference/rpc-arbitrum-debug_getbadblocks)
* [debug\_storagerangeat](https://docs.tatum.io/reference/rpc-arbitrum-debug_storagerangeat)
* [debug\_traceblockbyhash](https://docs.tatum.io/reference/rpc-arbitrum-debug_traceblockbyhash)
* [debug\_traceblockbynumber](https://docs.tatum.io/reference/rpc-arbitrum-debug_traceblockbynumber)
* [debug\_tracecall](https://docs.tatum.io/reference/rpc-arbitrum-debug_tracecall)
* [debug\_tracetransaction](https://docs.tatum.io/reference/rpc-arbitrum-debug_tracetransaction)

Users in need to retrieve older blocks (pre-nitro) need to use alternative methods:

* arbtrace\_block
* arbtrace\_callMany

## Example request and error with a "pre-nitro" block:

```json cURL
curl --location 'https://arb-one-mainnet.gateway.tatum.io' \
--header 'Content-Type: application/json' \
--header 'x-api-key: {API_KEY}' \
--data '{
    "jsonrpc": "2.0",
    "method": "debug_traceBlockByHash",
    "params": ["0xc99530cd6cd2dcb4e88bec85d8b97c67dcdd276918740604b6b097fe58f57fc7",
        {
            "tracer": "callTracer",
            "timeout": "1m"
        }
    ],
 "id": 1
}'
//response:
{
    "jsonrpc": "2.0",
    "id": 1,
    "error": {
        "code": -32000,
        "message": "missing trie node 0000000000000000000000000000000000000000000000000000000000000000 (path ) <nil>"
    }
}
```