Skip to main content
Important: We do not provide financial advice or custody funds. All transactions occur on third-party platforms.

Network Architecture: Nodes, Clients, and Sync

How a blockchain network actually runs — full nodes, light clients, archive nodes, propagation, and what it means to "run a node."

12 min · beginner · part of Blockchain: The Trust Machine

What Is a Node?

When people say "blockchain is decentralized," what they mean concretely is that the network is composed of many independent computers, called nodes, each running the same software and maintaining the same shared state. The properties of decentralization, censorship resistance, and trust-minimization come from the fact that no single party operates these nodes. They are run by individuals, companies, miners, exchanges, governments, and many others, distributed worldwide. A "node" in blockchain context is simply a computer running the network's software (like Bitcoin Core for Bitcoin, or Geth/Nethermind/Erigon for Ethereum). The node maintains a copy of the blockchain, validates new blocks and transactions according to the protocol rules, and relays them to other nodes. There are different types of nodes with different responsibilities: • **Full nodes** validate every block and every transaction independently, maintaining a complete copy of the blockchain. They are the backbone of decentralization. • **Mining/staking nodes** are full nodes that also participate in block production. They earn rewards. • **Archive nodes** are full nodes that additionally retain all historical state at every block height (rather than just the current state). Used for analytics and historical queries. • **Light clients (SPV nodes)** store only block headers and rely on full nodes for verification via Merkle proofs. Mobile wallets are typically light clients. • **Pruned nodes** validate everything but only retain recent blocks, deleting old data to save disk space. Modern Bitcoin Core can run as a pruned node with as little as 5 GB of disk. As of May 2026, Bitcoin has approximately 18,000 to 22,000 reachable full nodes worldwide (Bitnodes data), plus many more unreachable ones (behind firewalls, NATs, or Tor). The U.S. hosts about 10 percent of reachable nodes; Germany, France, Netherlands, Russia, and Canada round out the top of the list. Ethereum has approximately 13,900 unique node IPs, primarily running Geth, Nethermind, Reth, Besu, and Erigon clients. The number of nodes matters because more nodes means more independent verification, harder censorship, and more places where an honest copy of the chain exists. A blockchain run by ten cooperating nodes would be technically a blockchain but functionally a permissioned database. A blockchain with twenty thousand independent operators is much harder to compromise.

Also in this lesson

  • What Running a Node Actually Looks Like
  • Client Diversity and Why It Matters
  • How Transactions and Blocks Propagate
  • For Deeper Reading

Key terms

Node
A computer running blockchain network software. Maintains a copy of the chain, validates new transactions and blocks, and relays them to peers. The basic unit of blockchain infrastructure.
Full node
A node that independently validates every block and transaction, maintaining a complete copy of the blockchain. The backbone of decentralization.
Light client / SPV
A lightweight node that stores only block headers and verifies transactions via Merkle proofs from full nodes. Mobile wallets are typically light clients.
Archive node
A full node that additionally retains all historical state at every block height. Used for historical queries and analytics. Requires significantly more storage than a regular full node.
Pruned node
A full node that deletes old block data after validation, retaining only recent blocks. Saves disk space; Bitcoin Core can prune to as little as 5 GB.
Mempool
The "memory pool" of unconfirmed transactions waiting to be included in a block. Each node maintains its own mempool, which may differ slightly between nodes due to propagation delays.
Initial Block Download (IBD)
The process of syncing a fresh node from the genesis block to the current tip. Takes 1-7 days for Bitcoin, longer for Ethereum, depending on hardware.
Client diversity
The existence of multiple independent software implementations of the same blockchain protocol. Strengthens decentralization by preventing any single client bug from compromising the network.
Geth, Nethermind, Reth, Besu, Erigon
The major Ethereum execution client implementations. Geth has historically dominated; Nethermind, Reth, and others provide diversity.
Replace-by-Fee (RBF)
A Bitcoin feature allowing users to broadcast a new version of an unconfirmed transaction with a higher fee, replacing the original. Useful for unsticking transactions during fee spikes.
Gossip protocol
The peer-to-peer mechanism by which transactions and blocks propagate through a blockchain network. Each node forwards new data to its peers, who forward to their peers, etc.
Umbrel, Start9, MyNode, Citadel
User-friendly Linux distributions for running Bitcoin and Lightning nodes at home, designed for non-technical users.

Continue this lesson — 4 more sections in the CryptoBipto app.

Open lesson

Educational only — not financial advice.