How to Run an Archive Node & Use Cases

Most blockchain nodes forget on purpose. Full nodes prune old state data to stay lean, keeping only what’s needed to validate the current chain. It works fine until you need to ask a question like: “What was this wallet’s balance at block 14,000,000?” Suddenly, the answer is gone.

That’s where archive nodes come in. And that’s where NOWNodes saves you the infrastructure headache entirely.

What an Archive Node Actually Does

A standard full node keeps a rolling window of recent blockchain state. Older data gets pruned — deleted — to free up disk space. The node can still validate new blocks, but it can’t tell you what a smart contract’s storage looked like two years ago.

An archive node never prunes. From genesis block to today, every account balance, every contract state, every transaction result at every block height is retained in full. Both are useful; only one answers historical questions.

What an archive node retains:

  • Every block from genesis
  • Every historical account balance at any point in time
  • Every smart contract storage snapshot
  • Every transaction outcome at any block height

The tradeoff is disk space — Ethereum’s archive state alone runs into multiple terabytes — which is precisely why running one yourself is a significant operational commitment.

Running an Archive Node: The Reality

Spinning up your own archive node isn’t complicated in theory. For an EVM chain like Ethereum, you’d run a client like Erigon (which is optimized for archive storage) with –syncmode=full and –gcmode=archive. For Bitcoin-based chains, most implementations store full history by default. You point the client at a data directory, let it sync — which can take days to weeks — and then maintain it with enough storage headroom to keep growing.

The practical problem: you’re committing to tens of terabytes of disk, around-the-clock uptime, ongoing client upgrades, and the monitoring overhead to catch sync failures before your app breaks.
NOWNodes offers archive access via simple API endpoints — no node to run, no disk to provision, no sync to babysit. For Ethereum specifically, eth-archive.nownodes.io gives you a dedicated Erigon archive endpoint. Other chains with full archive support via NOWNodes include BTC, ETH, LTC, DOGE, ADA, Fantom, Optimism, zkSync, Starknet, VeChain, and dozens more.

If you need a chain that isn’t yet available in archive mode on shared infrastructure, NOWNodes supports dedicated node deployments.

Use Cases That Actually Need Archive Data

  • Blockchain explorers. Every time a user looks up a wallet’s transaction history or checks a contract’s state at a specific block, that’s an archive query. Without full historical state, you’re building on guesswork.
  • Analytics and research platforms. Charting TVL over time, tracking token distribution at launch versus today, modeling on-chain behavior across market cycles — none of this is possible from a pruned node. You need the full timeline.
  • Wallets and custodians. For compliance, auditing, or reconciliation, institutional custody often needs proof of a balance history. Archive access lets you recreate any snapshot of a point in time whenever you want.
  • Auditing smart contracts and DeFi protocols. To check that a liquidation was triggered correctly at a certain price and block, or to look at past governance votes, you need to query state that a full node no longer has.
  • Forensics and compliance. Tracing fund flows across wallets over months or years, building chain-of-custody evidence, flagging addresses that interacted with sanctioned protocols at specific points — this is archive territory.

Getting Archive Access with NOWNodes

If you’ve reached the point where standard nodes aren’t enough and you need access to historical blockchain state, archive nodes are the next step.
The path is straightforward. Sign up at nownodes.io, grab your API key, and start making calls against the archive endpoint for your chain of interest. For Ethereum method – eth_call: https://eth-archive.nownodes.io

Pass your API key as a header or query parameter, and you’re querying full historical state in minutes — not weeks. No client software, no storage procurement, no sync monitoring.

The Bottom Line

For chains where shared archive depth doesn’t meet your requirements, reach out to the team at [email protected]. Dedicated node deployments are available with custom configurations and SLA-backed uptime.The full list of supported chains and their archive availability is documented at nownodes.gitbook.io/documentation/archive-nodes.

Contact our team and we’ll help you get started, configure your endpoint, and offer ongoing support.

Submit a request through email. Our team will get back to you promptly. You can test our shared nodes NOW: just sign in and get your API Key!