Information

Archive Node Access

Conduit runs archive nodes for all supported networks. Full chain history from genesis is available on every plan with no surcharge.

What archive access means

You can query historical state at any block number, not just recent blocks. Methods that accept a block number or block tag parameter, such as eth_getBalance, eth_call, eth_getLogs, eth_getStorageAt, and eth_getCode, work against any block from genesis onward.

How to use it

Pass a specific block number (in hex) instead of "latest" in your request params.

Example: Get an address balance at block 1

Request
$curl -s https://[YOUR_RPC_URL]/[YOUR_API_KEY] -X POST \
>-H 'Content-Type: application/json' \
>-d '{"jsonrpc":"2.0","id":"1","method":"eth_getBalance","params":["0xYOUR_ADDRESS","0x1"]}'
Response
${"jsonrpc":"2.0","result":"0x1bc16d674ec80000","id":"1"}

Any valid hex block number from 0x0 onward is accepted.

Who needs archive access

  • Indexers - backfill historical on-chain events with eth_getLogs
  • Block explorers - look up balances and state at any historical block
  • Analytics tools - query token transfers, contract state, or gas usage over time
  • Audits and debugging - reproduce contract state at a specific block

Limitations

eth_getProof on OP Stack networks: Due to a known DoS vector in the underlying node software (Reth v2), eth_getProof is limited to a recent history window on OP Stack networks. Proofs for recent and latest blocks are unaffected. If you need proofs over a longer history window, contact support@conduit.xyz.