A blockchain node is a computer that runs the blockchain software, maintains a copy of the ledger, and validates transactions.
What Nodes Do
| Function | Description |
|---|---|
| Validate transactions | Check signatures, balances, and rules |
| Store the ledger | Keep a copy of the entire blockchain |
| Propagate data | Broadcast transactions and blocks to other nodes |
| Reach consensus | Agree on the state of the network |
| Serve data | Provide blockchain data to wallets and dApps |
Types of Nodes
| Node Type | Full Copy? | Validates? | Consensus? |
|---|---|---|---|
| Full node | Yes | Yes | Yes |
| Light node | No (headers only) | Limited | No |
| Archive node | Yes (full history) | Yes | Yes |
| Pruned node | Yes (recent only) | Yes | Yes |
| Validator node | Yes | Yes | Yes (PoS) |
| Mining node | Yes | Yes | Yes (PoW) |
Full Node
| Resource | Requirement |
|---|---|
| Storage (Ethereum) | 1TB+ SSD |
| Storage (Bitcoin) | 600GB+ |
| RAM | 8-16GB |
| Bandwidth | 500GB+/month |
| Uptime | Ideally 24/7 |
Running a full node supports the network but requires hardware and bandwidth.
Light Node
| Feature | Description |
|---|---|
| What it stores | Block headers only |
| How it validates | Assumes full nodes are correct |
| Storage | MBs, not GBs |
| Best for | Mobile wallets, resource-constrained devices |
Archive Node
| Feature | Description |
|---|---|
| What it stores | Full history + all intermediate states |
| Storage | 10TB+ |
| Best for | Block explorers, analytics, dApp developers |
Validator Node (Proof of Stake)
| Requirement | Ethereum |
|---|---|
| Minimum stake | 32 ETH |
| Hardware | Moderate |
| Reward | ~3-5% APY |
| Penalty for downtime | Slashing (loss of ETH) |
How Nodes Communicate
| Protocol | Purpose |
|---|---|
| Gossip protocol | Broadcast transactions and blocks |
| Handshake | Peer discovery |
| Sync protocol | Download and verify the blockchain |
| DevP2P (Ethereum) | Node-to-node communication |
Who Runs Nodes
| Entity | Typical Node |
|---|---|
| Exchanges | Full nodes for transaction verification |
| Block explorers | Archive nodes |
| Staking providers | Validator nodes |
| Developers | Full nodes for testing |
| Individuals | Full or light nodes |
Why Run Your Own Node
| Advantage | Why |
|---|---|
| Privacy | Don’t rely on third-party providers |
| Trust | Verify transactions yourself |
| Support the network | Strengthen decentralisation |
| No rate limits | Unlimited API access |
| Learn | Understand how blockchain works |
Why Not Run a Node
| Disadvantage | Why |
|---|---|
| Cost | Hardware, bandwidth, electricity |
| Maintenance | Updates, monitoring, troubleshooting |
| Time | Setup and maintenance take hours |
| No direct profit | Validators earn rewards; full nodes don’t |
Bottom Line
Nodes are the backbone of any blockchain. Full nodes store the entire ledger, validate transactions, and propagate data. Light nodes store only headers. Validator nodes secure proof-of-stake networks. Running your own node gives you privacy, full trust, and supports decentralisation, but requires hardware and maintenance. Most users rely on third-party nodes through wallets and exchanges.
What running a node actually means for you
The distinction between node types is not academic — it decides how independently you interact with the network. When you use a wallet that connects to a hosted full node run by a company, that company is telling you what the state of the blockchain is. It could in principle feed you false data, and it sees the addresses you query. Running your own full node removes both concerns: you verify blocks and transactions against the network yourself, and you never expose your queries to a third party. For most people that level of independence is not worth the setup cost, which is why the ecosystem comfortably supports a majority of users relying on trusted nodes. But for anyone holding significant value, verifying large transactions, or building on-chain tooling, the trade-off starts to look different.
The resource picture is the main barrier. An Ethereum full node on current specs wants more than a terabyte of SSD, 8-16GB of RAM, and a few hundred gigabytes of monthly bandwidth, and it works best running near-continuously. That is beyond the casual user but well within reach of a technically comfortable hobbyist. Bitcoin is a little lighter on RAM and available to run on dedicated hardware with 600GB of storage. If all of that sounds like more trouble than it is worth, you are in good company — but understanding why nodes matter still changes how you choose a wallet, because it tells you which provider you are trusting by default.
Why validators differ from full nodes
Proof-of-stake blurred a line that used to be clearer. On Bitcoin, mining and validation are the same act, and every full node also participates in consensus by accepting or rejecting blocks. On a proof-of-stake chain like Ethereum, consensus is handled by a separate group: validators who lock up a stake, propose and attest to blocks, and earn a reward of roughly 3-5% APY on that stake. The rest of the full nodes still validate everything, but they do not earn anything and do not face slashing risk. That is why a staking provider runs validator nodes while an individual hobbyist runs a plain full node with zero financial upside. The word “node” therefore covers everything from a tiny phone app to a staking warehouse, and knowing which one someone runs tells you what they are really doing for the network.
The honest decision process
Whether to run your own node comes down to a simple cost-benefit. Do you value privacy and full verification enough to maintain an always-on machine with terabyte storage and the patience for the occasional software update and troubleshooting session? If yes, running a full node or validator is a genuinely constructive hobby and a way to learn the protocol from the inside. If no — and that is the honest position for most users — then pick wallets and services that let you swap the provider, keep your own keys, and understand that you are trusting a third party for data. There is no wrong choice here, only a choice you should make deliberately rather than by accident. Either way, the network only functions because a decentralised minority runs nodes for everyone else, and supporting it directly is the purest form of contributing to the ecosystem short of being a validator.
Common questions
Q: Is running a full node profitable? A: Usually not. Validation is supported by volunteer hobbyists, businesses and exchanges that run full nodes for verification or to serve their users. Full nodes earn nothing; only validators on proof-of-stake chains earn staking rewards, and only mining nodes earn block rewards on proof-of-work chains.
Q: How difficult is it to set up a full node? A: It is a moderate technical project. You need the right hardware, a reliable internet connection with enough bandwidth, and a few hours to install and sync the software. Syncing the chain the first time can take days, and you will need to stay on top of updates and monitoring afterwards.
Q: Can I run a node on a normal laptop? A: For a light node, yes, easily. For a full node, only with caution: you need enough storage (1TB+ for Ethereum, 600GB+ for Bitcoin), 8-16GB of RAM, and ideally it should stay on rather than sleep. A laptop that is frequently closed will struggle to keep a full node in sync.
Q: What is an archive node used for? A: An archive node keeps not just the current state but the full history of intermediate states, which makes queries for past balances and states fast. Block explorers, analytics platforms and dApp developers rely on them, but they need 10TB+ of storage and are rarely run by individuals.