Full, light and archive nodes: who actually verifies the chain
Running a node is the difference between checking the rules yourself and trusting someone who did. Here is what each type stores, what it costs, and when it is worth it.
Reviewed by Mason Walker, Ethereum & Layer-2 · Last reviewed October 14, 2026
On this page
A node is a computer running the network's software, checking the rules for itself. A full node validates every block and transaction against consensus rules and keeps the current state. A light node checks headers and asks others for detail. An archive node keeps every historical state, which is what analytics and explorers need. Only some nodes also produce blocks — that role is separate and requires stake or hardware.
What does a full node actually do?
It downloads every block, verifies each transaction against the consensus rules — signatures, balances, formation — and rejects anything invalid regardless of who produced it. It maintains the current state, relays valid transactions and blocks to peers, and serves data to wallets that connect to it.
The political significance is larger than the technical one. Because full nodes independently enforce the rules, a change that node operators refuse to run does not take effect, no matter who proposes it. That distributed veto is the mechanism behind the claim that no single party controls a public chain.
How do light clients work?
A light client downloads block headers rather than full blocks, then requests cryptographic proofs that specific transactions are included. It verifies a great deal with very little data, which is what makes mobile wallets possible, but it must assume it is being told about all the relevant blocks by peers who could withhold information.
What is an archive node for?
A full node can prune older state once it is no longer needed for validation. An archive node keeps every historical state, so it can answer questions like what a contract's storage held at a block from two years ago. Explorers, analytics platforms and researchers depend on them; almost nobody else needs one.
| Type | Stores | Trust assumption | Typical use |
|---|---|---|---|
| Full node | All blocks, current state | Verifies everything itself | Self-sovereign wallets, businesses |
| Pruned full node | Recent blocks, current state | Same rules, less history | Home users with limited disk |
| Light client | Headers plus proofs | Relies on peers for availability | Mobile and embedded wallets |
| Archive node | All historical states | Verifies everything itself | Explorers, analytics, research |
How is a node different from a validator or miner?
Every validator runs a node, but not every node validates. Producing blocks requires either computational work or staked capital, plus the responsibilities that come with it — uptime obligations and, on proof-of-stake networks that implement it, penalties for misbehaviour. Running a node to check the chain carries none of those requirements, and none of the rewards. Our guide to proof of work versus proof of stake covers the block-production side.
What does it cost to run one?
- Storage is the binding constraint, and it grows continuously; an archive node needs an order of magnitude more than a full node.
- A solid-state drive is effectively required — mechanical drives cannot keep up with random reads during sync.
- Bandwidth matters, since a well-connected node uploads considerably more than it downloads.
- The initial sync is the slow part, taking hours to days depending on the chain and hardware.
- Ongoing effort is modest but non-zero: client updates matter, and a stale client can fall out of consensus.
Should you run one?
For most people, no — a reputable wallet provider's infrastructure is adequate and free. It becomes worth it when you want to verify your own balances without trusting anyone, when privacy matters and you would rather not tell a provider which addresses are yours, when you are building something, or when you want to hold the network to the rules you agreed to. Those are real reasons; earning is not one of them.
If you are analysing chain data rather than serving your own wallet, an archive node or a data provider is the tool — our on-chain analysis guide covers what those metrics do and where they mislead.
What does using your own node actually change?
Two things, both practical. First, verification: your wallet stops asking a company whether you have money and checks the chain itself, which removes an entire class of trust. Second, privacy: when you use a provider's infrastructure, that provider learns which addresses you care about, when you are online, and what you are about to do.
Neither benefit is dramatic on any single day, which is why most people never bother. They matter cumulatively, and they matter most in exactly the circumstances where a provider might behave differently from usual — outages, legal pressure, or a change of ownership.
- Point your wallet at your own node rather than the default endpoint.
- Expect a slower first sync and a stable experience afterwards.
- Keep the client updated; consensus changes are delivered as software releases.
- Remember a node at home reveals your IP to peers — use standard privacy tooling if that matters to you.
- 1. Nodes and clients — ethereum.org
- 2. Running a node — ethereum.org
- 3. Full node documentation — Bitcoin Core
Frequently asked
What is a full node?
Software that downloads and independently verifies every block and transaction against the consensus rules, maintains the current state, and relays valid data to peers.
Do I earn money by running a node?
No. Major networks pay no reward for running a node. Rewards go to block producers, which requires stake or mining hardware in addition to the node.
What is the difference between a full node and an archive node?
A full node keeps what it needs to validate and can prune old state. An archive node retains every historical state, which makes it far larger and is mainly useful for explorers and analytics.
Is a light client safe to use?
It offers strong guarantees for the data it checks, but it relies on peers to tell it about relevant blocks. For everyday amounts that is generally fine; for maximum assurance a full node is the stronger position.
How much disk space does a node need?
It varies by chain and grows over time. Expect hundreds of gigabytes for a typical full node and several times that for an archive node, always on a solid-state drive.
Lauren Bennett is a Senior Bitcoin Analyst at Crypto Almanac Daily, specializing in Bitcoin market structure, on-chain analytics, mining economics, institutional adoption, spot ETF developments, and macroeconomic trends shaping digital assets. Her reporting focuses on translating complex blockchain data into clear, data-driven insights for investors, industry professionals, and readers following the evolution of the Bitcoin ecosystem. Lauren regularly analyzes network activity, miner behavior, liquidity trends, exchange flows, and the impact of monetary policy on digital asset markets. Before joining Crypto Almanac Daily, she covered financial markets and emerging technologies, developing expertise in blockchain infrastructure and digital asset research. Her work emphasizes factual reporting, transparent analysis, and long-term market fundamentals rather than short-term speculation. At Crypto Almanac Daily, Lauren contributes daily news coverage, in-depth market analysis, educational explainers, and feature articles that help readers better understand Bitcoin's role in the global financial system and the rapidly evolving digital asset economy.
This guide is educational and general in nature. It is not financial, investment, legal or tax advice, and it does not account for your circumstances. Crypto assets are volatile and you can lose the money you put in. See our editorial policy and methodology.
