What is a Node?
A node is a computer (or server) that runs blockchain client software and connects to the peer-to-peer network, contributing to the blockchain’s operation by validating and propagating transactions, verifying blocks, and maintaining a copy of the chain’s data. Nodes are the physical infrastructure of any blockchain—without nodes, there is no network. The degree of decentralization, security, and censorship resistance of a blockchain is directly determined by the number, geographic distribution, and independence of its nodes.
There are several types of nodes with different roles and resource requirements. Not every node participates in consensus (that role is reserved for validators/miners). The most basic node—a full node—simply downloads, validates, and stores all blocks and transactions, making it possible to independently verify the entire chain without trusting any third party. Running a full node is the gold standard for trustless interaction with a blockchain: if you run a full node, you don’t need to trust RPC providers, block explorers, or any other intermediary—you can verify everything yourself.
As of early 2025, Ethereum has an estimated 6,000–8,000 reachable full nodes (down from ~12,000 in 2022, partly due to the increasing storage requirements of operating a full node). Bitcoin has approximately 18,000–20,000 reachable nodes. Solana has approximately 1,900 validator nodes but far fewer non-validating full nodes due to the hardware requirements (a Solana full node needs a high-end server with 128+ GB RAM and 12+ TB NVMe storage).
How It Works
Types of Nodes
Full Node downloads and validates every block and transaction from the genesis block to the current chain tip. It maintains the full state trie (the current state of all accounts, contracts, and storage) and can independently verify any transaction without external help. On Ethereum, a full node requires:
- Storage: ~2.5 TB (as of early 2025, growing ~100 GB per year with pruning)
- RAM: 16–32 GB recommended
- CPU: Modern multi-core processor
- Bandwidth: 10+ Mbps sustained
- Sync time: 1–3 days from genesis (or hours with snapshots)
Full nodes participate in the peer-to-peer gossip network, propagating new transactions and blocks to other nodes. They can also serve RPC requests (if configured) and provide data to light clients.
Archive Node is a full node that additionally stores all historical states—not just the current state, but every intermediate state at every block. This means an archive node can answer queries like “What was the balance of this address at block 15,000,000?” without reconstructing the state from genesis. Archive nodes require significantly more storage:
- Ethereum: ~12–15 TB (growing ~2 TB per year)
- RAM: 64+ GB recommended
- CPU: High-end server-grade processor
Archive nodes are primarily used by block explorers (Etherscan), indexers (The Graph, Dune), analytics platforms, and security researchers. Most individual users do not need to run archive nodes—pruned full nodes provide the same security guarantees with much less storage.
Light Node (or light client) downloads only block headers (80 bytes each vs. the ~50–100 KB of a full block) and verifies data availability by requesting Merkle proofs for specific transactions. Light nodes cannot independently verify the entire chain but can verify that specific transactions are included in valid blocks. They require:
- Storage: ~100–500 MB (Ethereum headers only)
- RAM: 256 MB–1 GB
- Bandwidth: Minimal (requesting only specific proofs)
Ethereum’s Helios, Loquax, and Nimbus light clients can verify the chain using only block headers and validator signatures, requiring less than 100 MB of storage. These are designed to run on mobile devices and embedded systems.
Validator Node is a full node (or node cluster) that additionally participates in the consensus protocol. On Ethereum, a validator stakes 32 ETH and is responsible for proposing blocks, attesting to blocks, and participating in sync committees. The hardware requirements are higher than a standard full node because missed attestations result in slashing penalties:
- Storage: ~2.5 TB + monitoring data
- RAM: 32–64 GB
- CPU: 8+ cores recommended
- Uptime: 99.5%+ required to avoid minor penalties
- Network: Low-latency, stable connection
Mining Node (Bitcoin, pre-Merge Ethereum) is a full node that also runs mining software to solve proof-of-work puzzles. On Bitcoin, miners compete to find a hash below the current difficulty target, and the first to find it gets to propose the next block and collect the block reward (currently 3.125 BTC post-halving in April 2024). Mining nodes require specialized ASIC hardware (SHA-256 miners for Bitcoin), which cost $2,000–15,000 per unit and consume significant electricity.
Node Software (Ethereum Client Diversity)
Ethereum’s decentralization benefits from having multiple independent client implementations. This is critical because if all nodes run the same software, a bug in that software could take down the entire network. Different implementations are written in different programming languages by different teams, making shared bugs extremely unlikely.
| Client | Language | Type | Market Share (2025) |
|---|---|---|---|
| Geth | Go | Execution + Consensus | ~60% of execution clients |
| Nethermind | C# | Execution | ~20% of execution clients |
| Erigon | Go | Execution (archive-focused) | ~10% of execution clients |
| Reth | Rust | Execution (new, by Paradigm) | ~5% of execution clients |
| Besu | Java | Execution (enterprise) | ~5% of execution clients |
| Lodestar | TypeScript | Consensus (beacon) | ~15% of consensus clients |
| Lighthouse | Rust | Consensus (beacon) | ~35% of consensus clients |
| Prysm | Go | Consensus (beacon) | ~40% of consensus clients |
| Nimbus | Nim | Consensus (beacon) | ~10% of consensus clients |
The “client diversity” principle is a critical security consideration. The Ethereum community actively monitors client distribution—if one client exceeds 50% (execution) or 33% (consensus) market share, it is considered a safety risk. Geth’s historical dominance (~75%+ before 2023) was a known concern, and the community has actively encouraged adoption of alternative clients like Reth and Nethermind.
Node Sync Methods
When a node first joins the network, it must synchronize with the existing chain. The main sync methods:
- Full sync: Download and verify every block from genesis. Most secure but slowest (days for Ethereum).
- Snap sync: Download state snapshots and recent blocks, then verify recent blocks. Faster (hours) but requires trusting that the snapshot is valid.
- Checkpoint sync: Start from a recent finalized checkpoint (verified by the consensus layer). Fastest (minutes) and very secure, as the checkpoint has already been attested by 2/3 of validators.
- Archive sync: Like full sync, but retains all historical state. Slowest and requires the most storage.
Real-World Examples
Ethereum nodes form the backbone of the world’s largest smart contract platform. The Ethereum Foundation runs several “boot nodes” that help new nodes discover peers. Cloud providers like Infura, Alchemy, and QuickNode operate large node clusters that serve millions of RPC requests per day. However, reliance on centralized RPC providers creates a centralization risk—if Infura goes down, every dApp using it fails simultaneously. This happened in November 2020 when Infura experienced an outage that affected major dApps including Uniswap and MetaMask.
Bitcoin nodes are the most decentralized in terms of individual operators. The Bitcoin Core software (written in C++) is the dominant client with >99% market share, which is a known concern. The project has been criticized for client monoculture, though alternatives like btcd (Go) and Libbitcoin (C++) exist. Bitcoin’s lower hardware requirements (a full node needs ~800 GB storage and 8 GB RAM) make it feasible for individuals to run nodes on consumer hardware.
Solana validators require significantly more resources than most other chains. A Solana validator needs a high-end server with 128+ GB RAM, 12+ TB of NVMe storage (PCIe Gen4), and a 12+ core CPU. This hardware requirement (estimated cost: $5,000–15,000 per node) limits the number of independent validators and is one of the most common criticisms of Solana’s architecture. However, the Firedancer validator client (written in C by Jump Crypto) has demonstrated significantly lower resource usage in testing.
Home staking on Ethereum has become increasingly accessible. As of early 2025, over 80,000 individuals run their own Ethereum validators (either solo or through Distributed Validator Technology like Obol and SSV). The rise of “DVT” (Distributed Validator Technology) allows a single validator to be split across multiple machines operated by different people, reducing the risk of a single point of failure for home stakers.
Key Risks / Considerations
- Hardware requirements are growing: Ethereum’s state grows ~100 GB per year. If growth continues, running a full node will require increasingly expensive hardware, potentially centralizing node operation among those who can afford it.
- Client diversity is fragile: Geth’s market share (60%) means a Geth bug could potentially affect 60% of the network. The Ethereum community actively monitors this and recommends alternative clients.
- RPC provider centralization: Most dApps use centralized RPC providers (Infura, Alchemy) rather than their own nodes. This creates a single point of failure and allows RPC providers to censor transactions.
- State rent / expiry: Ethereum has proposed EIP-4444 (state expiry) to address state growth by expiring old state and requiring archive nodes to store it. This would reduce full node requirements but create dependency on archive infrastructure.
- Light client verification: While light clients improve accessibility, they inherently trust full nodes for state verification. The security of light clients depends on the existence of honest full nodes in the network.
Frequently Asked Questions
Q: What’s the difference between a node and a validator? A: Every validator runs a node (usually multiple nodes), but not every node is a validator. A node validates and stores the chain. A validator additionally participates in consensus by proposing and attesting to blocks, which requires staking (32 ETH on Ethereum). Validators are economically incentivized and penalized for misbehavior; regular nodes face no penalties.
Q: Should I run my own node? A: If you’re a developer building on Ethereum, running your own node provides more reliable RPC access and eliminates dependence on centralized providers. If you’re an individual user, running a node improves your privacy (you don’t need to trust RPC providers with your queries) and contributes to network decentralization. However, it requires technical knowledge, stable internet, and dedicated hardware.
Q: How long does it take to sync an Ethereum full node? A: With checkpoint sync (starting from a recent finalized checkpoint), syncing an Ethereum full node takes 4–12 hours on a modern machine with a fast SSD and 500+ Mbps connection. Full sync from genesis takes 1–3 days. Archive sync from genesis takes 1–2 weeks and requires 12+ TB of storage.
Q: Can I run a node on a Raspberry Pi? A: For Bitcoin, yes—a Raspberry Pi 4 or 5 with an external SSD can run a pruned full node. For Ethereum, it’s technically possible but not recommended due to RAM requirements (16 GB minimum for a pruned node, which Pi doesn’t have) and slow I/O. However, an Ethereum light client can run on a Pi or even a smartphone.