BlockReq
Back to Home

Ethereum Archive Node RPCFull history archive with eth_getProof, stateOverride & debug/trace

Ethereum archive node RPC with eth_getProof on any block, stateOverride, debug_traceTransaction. Full history since genesis. Free 80M RU/month.

MainnetSepolia TestnetBeacon Chain
Get Started FreeContact Us

Why Ethereum Archive on BlockReq

  • Full history since genesis block (block 0)
  • eth_getProof on any historical block — no block limits
  • eth_call with stateOverride for contract simulation
  • debug_traceTransaction with all tracer types
  • Sub-100ms P95 latency with global routing
  • No 'missing trie node' errors — complete state retained

Supported Archive RPC Methods

All methods work on any historical block — from genesis to latest.

eth_getBalance
eth_getCode
eth_getStorageAt
eth_getProof
eth_call (stateOverride)
debug_traceTransaction
debug_traceCall
trace_block
trace_transaction
eth_getLogs

eth_getProof on any Ethereum block

bash
curl -X POST https://eth.blockreq.com/YOUR_API_KEY \
  -H "Content-Type: application/json" \
  -d '{
    "jsonrpc": "2.0",
    "method": "eth_getProof",
    "params": [
      "0xdAC17F958D2ee523a2206206994597C13D831ec7",
      ["0x0"],
      "0xF4240"
    ],
    "id": 1
  }'

Frequently Asked Questions

Does BlockReq support eth_getProof on Ethereum for all historical blocks?

Yes. BlockReq runs full archive nodes for Ethereum, so eth_getProof works on any block from genesis to latest. There are no block-range limitations.

Can I use stateOverride with eth_call on Ethereum archive nodes?

Yes. BlockReq supports eth_call with stateOverride on Ethereum, allowing you to simulate transactions with modified contract state, balances, or bytecode without sending actual transactions.

What debug and trace methods are available on Ethereum?

BlockReq supports debug_traceTransaction, debug_traceCall, trace_block, trace_transaction, and trace_replayBlockTransactions on Ethereum archive nodes.

How do I fix 'missing trie node' errors on Ethereum?

The 'missing trie node' error occurs when querying historical state on pruned (non-archive) nodes, which only retain the last 128 blocks. BlockReq archive nodes store complete state since genesis, eliminating this error for any block query.

Can I use Hardhat mainnet forking with BlockReq Ethereum archive nodes?

Yes. BlockReq archive nodes are ideal for Hardhat forking because you can fork from any historical block without 'missing trie node' or 'header not found' errors. Pin any block number in your hardhat.config.js for consistent testing.

Start using Ethereum archive nodes today

Free 80M RU/month. No credit card required. Archive nodes with eth_getProof, stateOverride, and debug/trace on every plan.

Get Started Free →