What is a blockchain node?

What does a blockchain node do?

ethereum.org defines a node as any instance of the client software that is connected to other computers running the same software, forming a network. The client is the program itself: an implementation of the protocol that checks data against the rules. Bitcoin.org describes a full node in similar terms — a program that fully validates transactions and blocks.

That gives nodes three jobs. They store a copy of the ledger; they verify every new transaction and block, rejecting anything that breaks the rules, such as spending coins twice; and they relay valid data to their peers, so news of a payment spreads across the network. Miners and validators also run nodes, but most nodes do neither — they simply check. That independent checking is what stops a powerful miner or validator from slipping in an invalid block: the rest of the network will refuse it (see proof of work vs proof of stake).

What types of nodes are there?

Nodes differ mainly in how much data they keep and how much they verify themselves.

The light-node idea goes back to the Bitcoin whitepaper, which described simplified payment verification: a user keeps only block headers and checks that a transaction is included in a block, without running a full node. The trade-off is trust — a light node relies on full nodes to answer honestly. A block explorer lets you look up that history in a browser, but you are then trusting whoever runs it.

What does it take to run a Bitcoin or Ethereum node?

Requirements change as chains grow, so treat these as a snapshot from the official sources, checked October 2026.

Bitcoin. Bitcoin Core's current settings assume a blockchain of about 897 GB. Bitcoin.org's guide lists modest minimums otherwise — 2 GB of memory, an upload speed of at least 400 kilobits per second, about 20 GB of download a month after an initial download of roughly 740 GB, and at least six hours a day online. Turning on pruning cuts disk use to around 7 GB while still verifying every block.

Ethereum. Every Ethereum node runs two programs: an execution client, which processes transactions and holds the current state, and a consensus client, which follows proof of stake. ethereum.org's minimum is a 2+ core CPU, 16 GB of RAM (32 GB recommended), a 2 TB NVMe SSD and 25 Mbit/s or more of bandwidth. By client, a Geth node synced the default way needs 500 GB or more, plus roughly 200 GB for the consensus client's data; an archive node runs to 12 TB or more.

Why would anyone run their own node?

ethereum.org gives two kinds of reasons. For you: you can verify data yourself instead of trusting someone else's answer about your balance, and you avoid leaking your addresses and balances to intermediaries whose servers your wallet would otherwise query. For the network: more independent nodes mean more copies of the rules being enforced and more peers for light clients to connect to. Bitcoin.org adds that if too few people run nodes, lightweight wallets have to fall back on centralized services.

1. Pick the client software from the project's official site, and verify the download.

2. Check your hardware and data plan against the current requirements, including disk growth.

3. Let it sync. The first download and verification can take a long time.

4. Point your wallet at it so balance checks and broadcasts go through your own machine.

5. Keep it updated. Client updates carry fixes and, sometimes, rule changes the network has adopted.

Is running a node the same as staking or mining?

No. A node verifies; a miner or validator also produces blocks. ethereum.org is explicit that running a node does not require 32 ETH — staking is a separate, optional step that adds validator software and a deposit on top of a node. A Bitcoin full node likewise does no mining; it simply refuses to accept blocks that break the rules, whoever mined them. You can read more in what is staking and how Bitcoin mining works.

What mistakes do beginners make about nodes?

• Thinking a wallet app is a node. Most wallets connect to nodes run by the wallet company or another provider.
• Confusing nodes with miners or validators. All of them run nodes, but most nodes only verify.
• Underestimating disk growth. Chains grow; ethereum.org notes its 2 TB minimum is likely to be exceeded by 2027.
• Downloading clients from unofficial links. Tampered downloads are a known attack route; see common crypto scams.
• Assuming a light node gives the same guarantees as a full node. It trusts full nodes for most data.