A blockchain node is a computer running a network's software, keeping a copy of the chain and checking new blocks against the rules. Full nodes verify everything themselves, light nodes check only block headers and ask others for the rest, and archive nodes keep every historical state. People run their own node to verify their own transactions, to keep their addresses private from third parties, and to strengthen the network.
What does a node actually do?
A node downloads blocks, checks that each one follows the protocol's rules, and passes valid data on to its peers. Bitcoin.org defines a full node as "a program that fully validates transactions and blocks". Most also relay transactions and serve data to lighter software.
That checking is what keeps a blockchain honest. Every full node recomputes the same result from the same data. If a block pays its producer too much, spends coins twice or carries an invalid signature, each node rejects it on its own, no matter who produced it. A node checks block links with a hash function, and signatures with public-key cryptography.
On Ethereum, "node" means a pair of programs. Ethereum's documentation says a node has to run two clients: an execution client, which runs transactions in the Ethereum Virtual Machine and holds the current state, and a consensus client, which follows proof-of-stake consensus. A client is simply one implementation of the protocol, such as Geth or Nethermind on the execution side.
Full, light and archive nodes: what's the difference?
Node types differ in how much they store and how much they verify for themselves.
| Type | What it keeps | What it verifies | Trust it needs | Typical user |
|---|---|---|---|---|
| Full node | Every block it needs to validate the chain, with older state often pruned | Every block and transaction | None beyond its own software | Individuals, businesses, validators |
| Light node | Block headers only | That data matches the headers | That full nodes are not hiding data | Phones, browser wallets |
| Archive node | Everything, including every past state | Every block from the start | None beyond its own software | Block explorers, analytics firms |
Full nodes. On Ethereum, a full node typically keeps state for the most recent 128 blocks and prunes older state, which it can regenerate if needed. Bitcoin Core can run in pruned mode, which cuts disk use from over 750 GB to around 7 GB while still validating everything. Pruning saves space, not security.
Light nodes. A light client downloads only block headers. In Bitcoin, a header is 80 bytes, or up to 4.2 MB a year. The client can prove a transaction is in a block using a Merkle tree branch, but Bitcoin's developer guide notes this "does not guarantee validity" of the transactions inside. A light client also depends on full nodes to send it data, and they can withhold transactions.
Archive nodes. These keep every historical state, so you can ask what any account held at any past block. Disk needs vary a lot by client. Ethereum.org's client table lists full archives from about 2 TB with Geth's newer format to 14 TB or more with Nethermind.
Is a validator the same as a node?
No. Every validator runs a node, but most nodes are not validators.
A validator is extra software that proposes and votes on blocks in a proof-of-stake network, with money at stake. On Ethereum, a validator is an add-on to the consensus client, and solo validating needs a deposit of 32 ETH. A validator that breaks the rules can be slashed, losing part of its stake. A plain full node has nothing at stake and earns nothing. It only checks.
Bitcoin works the same way. Miners produce blocks, but they need full nodes to accept them. A miner that breaks the rules has wasted its electricity, because nodes ignore the block.
Light nodes can't be validators on Ethereum, because they don't take part in consensus. If you want to earn staking rewards yourself, you need a full node first.
Why would you run your own node?
Running your own node changes who you have to trust. There are four practical reasons.
- Verification. Your node checks every rule itself. When your wallet shows a payment as confirmed, it is your own copy of the chain saying so. Ethereum.org's summary of the idea is "Don't trust, verify."
- Privacy. A wallet that queries someone else's server reveals which addresses it cares about. Ethereum.org notes that your own node avoids leaking your addresses and balances to intermediaries. For light clients, Bitcoin's developer guide calls this kind of address request "a large privacy leak".
- Independence. Most wallets reach the chain through a hosted RPC node run by a company. If that company goes down, so does your access, even though the blockchain is fine.
- Your vote on the rules. Nodes decide which blocks are valid. During a disputed hard fork, the software people choose to run decides which chain they follow.
There's also a benefit to everyone else. Ethereum.org notes that a full node helps the whole network even if it never validates, because a larger, more varied set of nodes is harder to censor or take down.
What happens when everyone relies on the same node?
The best-known example of shared-node risk happened on November 11, 2020. Infura, which provides Ethereum node access to many apps, suffered an outage. Parts of its system ran older versions of the Geth client that hit "a critical consensus bug at block 11234873." Versions 1.9.19 and later were unaffected.
The chain itself kept running on up-to-date nodes. But according to The Block's report, MetaMask had problems because Infura was its default provider, and Binance temporarily halted ETH and ERC-20 withdrawals. Infura said all systems had recovered by 14:42 UTC.
People running current software on their own nodes kept working throughout. The lesson is about dependency more than any single company: when thousands of users share one node provider, that provider's bug becomes their bug too.
How much hardware does a node need?
It depends heavily on the chain, and the gap between networks is large. The figures below come from each project's documentation as of November 2026.
| Setup | Disk | Memory | Network |
|---|---|---|---|
| Bitcoin full node | Over 750 GB (about 7 GB if pruned) | 2 GB minimum | About 740 GB to sync, then about 20 GB a month down |
| Ethereum full node | 4 TB NVMe SSD | 16 GB minimum, 32 GB recommended | 25 Mbit/s minimum |
| Ethereum validator | 4 TB NVMe SSD | 64 GB suggested | 25 Mbit/s or more upload |
| Solana validator | Several separate NVMe drives of 1 TB or more | 256 GB or more | At least 2 Gbit/s if staked |
Sources: Bitcoin.org, Ethereum.org and Anza's Solana validator requirements.
A worked example shows what the Bitcoin numbers mean at home. Say your internet plan has a 1 TB monthly cap.
- First month: the initial sync downloads about 740 GB. That uses about 74% of your cap before any other use.
- Every month after: about 20 GB down. Bitcoin.org also notes nodes on fast connections often upload 200 GB or more a month, though you can limit that in the settings.
- Disk: a 2 TB drive leaves room for growth. In pruned mode, a small drive is enough.
The Ethereum and Solana rows show a design choice. Ethereum keeps requirements within reach of a well-specified home computer. Solana's documentation lists data-center-class machines, which buys speed but means fewer people can run a validator from home.
The disk needs also change over time. Ethereum clients can now drop older history: with rolling history expiry, ethereum.org gives roughly 400 to 650 GB for supported clients, and Geth doesn't support that mode yet. Requirements are a moving target, so check your client's own documentation before buying hardware.
What are the downsides of running a node?
A node is a commitment, not a one-time setup.
- Maintenance. You need to update the software. The Infura outage shows what happens when nodes fall behind. Before a network upgrade, an outdated node can end up on the wrong chain.
- Exposure. Bitcoin.org warns that a node joins a public network, so attackers may target its users. Keep the machine patched, and don't run it on the computer that holds your savings.
- No wallet protection. Running a node does not secure your keys. Bitcoin.org says the same precautions apply as with any wallet, so your seed phrase still needs safe storage.
- Validator risk. A plain node risks nothing. A validator can lose rewards when offline and be slashed for breaking the rules, so ethereum.org advises minimizing downtime.
If you want a simpler start, ethereum.org lists plug-and-play machines as the most straightforward option, and single-board computers such as the Raspberry Pi as a cheap but limited one. For Bitcoin, pruned mode on an ordinary laptop or desktop works. Running a Lightning node adds more upkeep on top.
More guides are in our nodes hub, and the Bitcoin and Ethereum hubs cover the networks themselves.
Key takeaways
- A node is a computer running a blockchain's software, and a full node checks every block and transaction against the rules itself.
- Light nodes check only headers and depend on full nodes for data, while archive nodes keep every past state for explorers and analytics.
- Validators are nodes with money at stake that propose and vote on blocks. Most nodes only verify and earn nothing.
- Your own node gives you independent verification, more privacy than a shared server, and no dependence on one provider's uptime.
- Requirements range from a pruned Bitcoin node on a laptop to Solana validators that need 256 GB of memory, so check current client documentation first.
Sources
Get the weekly commit
New blockchain deep dives every week.

