> For the complete documentation index, see [llms.txt](https://docs.fastnode.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fastnode.io/advanced/archive-nodes.md).

# Archive Nodes

This page explains how archive nodes differ from full nodes, how pruning works, and what historical data you can access.

## Archive vs. full nodes

**Archive nodes** store the complete historical state of the blockchain from the genesis block — every block, state, balance, and storage value, with nothing pruned. **Full nodes** keep only the recent state required for current network operations and prune older data to save disk space.

Use an archive node when you need to:

* Read an account balance or contract state **at a historical block**.
* Replay or trace old transactions.
* Build analytics, indexers, or explorers that need deep history.

## Endpoint format

Archive networks use an `-archive` suffix:

```
https://eth-archive.fastnode.cc/YOUR-API-KEY/
```

## Example: balance at a historical block

```bash
curl --location 'https://eth-archive.fastnode.cc/YOUR-API-KEY/' \
  --header 'Content-Type: application/json' \
  --data '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "eth_getBalance",
    "params": ["0xADDRESS", "0x100000"]
  }'
```

Against a full node the same call for an old block returns a "missing trie node" error; against an archive node it resolves correctly.

## Availability

Archive depth varies by network. Each chain's page notes whether archive access is available.

{% hint style="info" %}
If a shared network doesn't offer enough depth for your use case, request expanded history at **<support@fastnode.io>**, or deploy a dedicated archive node from the dashboard.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.fastnode.io/advanced/archive-nodes.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.