What Is a Blockchain Node?

A blockchain node is a computer running network software to verify and relay transactions. Learn how full nodes, light nodes, and clients operate.

Updated September 2026 · Reviewed by the PipeFlare team

A blockchain node is a computer running dedicated software that connects to the network, stores or verifies chain data, and relays transactions and blocks to its peers.

Running a node lets you verify transactions and enforce network rules directly on your own machine instead of trusting a third-party server or commercial provider.

About blockchain node

A blockchain node is a computer running dedicated software that joins a peer-to-peer network to store or verify chain data and relay transactions and blocks to other participants. When you submit a transfer or query an account balance, you are asking a node to check the ledger state. Most people interact with blockchain networks through wallet applications that silently route their requests through a remote node managed by an infrastructure provider. Setting up and running your own node replaces that trust assumption with direct mathematical verification. You validate every protocol rule and transaction locally on your own machine. Running a node is fundamentally about privacy and sovereign verification rather than earning financial rewards.

How it actually works

At its core, a blockchain node is a computer running specialized software that connects to a decentralized network of peer computers over the internet. When a user creates a transaction, their device broadcasts that transaction to nearby nodes. Each node that receives the transaction validates its cryptographic signature, checks that the sender holds sufficient funds, and verifies that the transaction adheres to all protocol rules. If valid, the node stores the transaction in its local memory pool and broadcasts it to other connected peers. When a miner or validator packages pending transactions into a new block, that block is propagated across the entire network. Every independent node downloads the new block, checks that every contained transaction is legitimate, confirms that the block header meets all consensus requirements, and updates its local copy of the blockchain ledger. Any proposed block or transaction that breaks protocol rules is discarded immediately by conforming nodes, preventing invalid state changes without relying on a central authority.

Ethereum.org categorizes network nodes into three primary tiers: full nodes, light nodes, and archive nodes. A full node is the standard operational backbone of the network. It downloads blocks sequentially, validates transactions and state transitions against protocol rules, stores recent state data, and serves blockchain data to peers upon request. A light node offers an alternative verification path designed for resource-constrained hardware. Instead of downloading every transaction and state change, a light node downloads only block headers and verifies specific data against cryptographic state roots embedded within those headers. This approach needs far less storage and bandwidth, although light nodes must request state data from full nodes to perform lookups. An archive node represents the most resource-intensive tier. It is a full node configured to build and preserve an uninterrupted historical ledger of every account balance, storage slot, and contract state from the genesis block to the current chain tip. While standard full nodes prune older intermediate states to save disk space, archive nodes retain all historical data permanently, which is why block explorers, analytics platforms, and developers auditing historical contract activity use them.

The internal software architecture required to operate a node varies across blockchain protocols. On Bitcoin, software distributed through Bitcoin.org functions as a single unified program. The node client independently downloads the entire history of the Bitcoin blockchain, validates every spending script, and monitors network peers directly. On Ethereum, a modern node splits these responsibilities across two decoupled software programs: an execution client and a consensus client. The execution client processes transaction computations, handles smart-contract logic, updates state storage, and manages user transaction pools. The consensus client implements the Proof of Stake (PoS) consensus engine described in Ethereum.org's PoS documentation. It tracks the canonical chain tip, participates in peer-to-peer communication, and processes block attestations. These two clients run side by side on the same physical or virtual machine, communicating locally to ensure that every proposed state transition complies with consensus rules before updating the ledger.

Most day-to-day cryptocurrency interactions do not involve personal node administration. Standard crypto wallet applications and web interfaces typically point to remote nodes maintained by third-party infrastructure companies or centralized exchanges. While remote nodes eliminate the need to download large amounts of blockchain data, they introduce subtle tradeoffs in privacy and trust. When you query an address or broadcast a transfer through a third party's remote node, that provider can see your requests and transaction activity. Directing your wallet to your own private node eliminates this intermediary, enabling self-sovereign verification where you confirm your own balances and broadcast transactions without third-party observation. Furthermore, operating a node must not be confused with operating a validator or a miner. A node purely verifies data and shares information across the network. It does not produce blocks or earn native protocol yields on its own. Validating on Proof of Stake networks or mining on Proof of Work (PoW) networks are distinct operational duties that require a node as underlying infrastructure, as explored in the guide on staking vs mining and what is a blockchain validator.

Start here

1Define your personal objective before provisioning equipment. If you want to verify your own transactions privately without relying on third-party servers, running an independent full node achieves full sovereignty without requiring any staking collateral or validator keys.
2Check the official hardware, storage, and bandwidth specifications for your chosen blockchain. Ledger histories expand continuously over time as new blocks are added to the chain. Visit [Bitcoin.org](https://bitcoin.org/en/full-node) or [Ethereum.org](https://ethereum.org/en/developers/docs/nodes-and-clients/) to review current disk capacity, memory, and data transfer requirements, as exact figures vary by protocol and change regularly.
3Choose and install network client software. For a Bitcoin node, download a reputable open-source implementation. For an Ethereum node, select both an execution client and a consensus client from the supported options documented on Ethereum.org, ensuring both clients are configured to communicate locally.
4Connect the machine to the internet and begin the initial synchronization process. The client software will download, process, and validate the blockchain's historical blocks from connected peers. This verification phase takes time and bandwidth; the requirements vary by chain and change over time.
5Connect your cryptocurrency wallet to your local node endpoint. Navigate to your wallet settings, locate the custom network or Remote Procedure Call (RPC) configuration, and enter your local node's IP address. This routes all future balance checks and transaction broadcasts directly through your own verified node software.

Strengths

Direct cryptographic verification ensures you never have to trust an external block explorer, centralized exchange, or commercial infrastructure provider to confirm that an incoming transaction is authentic.
Better privacy, because querying account balances and broadcasting transactions through your own node prevents third-party RPC providers from logging your IP address alongside your wallet public keys.
Strengthens overall network resilience and decentralization by adding another independently validating ledger replica that enforces consensus rules.

Common misunderstandings

Running a standard node earns no economic yield or transaction fee rewards, meaning all hardware costs, storage drives, and electricity usage remain entirely self-funded operational expenses.
Ongoing maintenance and storage expansion are necessary as the blockchain ledger grows continuously with every newly confirmed block, requiring reliable broadband connections and periodic software client updates.
Initial synchronization requires substantial time and resources, as downloading and cryptographically validating years of chain history places high demands on local processing power, storage speed, and bandwidth.

Common questions

What is the difference between a full node and a light node?

A full node downloads, stores, and validates all block data and transactions against the network consensus rules from the genesis block forward. It maintains local state data and can serve information to other peers across the network. A light node downloads only block headers and verifies specific account data against state roots contained in those headers. Because a light node does not validate every transaction or retain the full ledger, it operates with modest hardware and minimal storage. The tradeoff is that light nodes must query full nodes to retrieve cryptographic proofs whenever they need account details.

Do blockchain nodes earn money?

No, running a standard blockchain node does not generate revenue or token payouts. A node exists to independently verify chain rules, store ledger history, and propagate transactions across the peer-to-peer network. In order to earn rewards, a participant must take on a dedicated block-production role that builds on top of a node. On Proof of Work networks, this requires operating specialized mining hardware. On Proof of Stake networks, it requires depositing capital as a validator. A node alone is purely an infrastructure and verification tool.

Is a node the same as a validator?

A node is not the same as a validator. A node is a computer running client software that connects to peers, validates transaction rules, and maintains a copy of the blockchain ledger. A validator is an entity on a Proof of Stake (PoS) network that locks up financial stake to propose and vote on new blocks. Every active validator must run or connect to a node to receive network data and submit attestations. However, many nodes operate independently without staking tokens, producing blocks, or participating in validator duties. For more on this role, see the guide on what is a blockchain validator.

Do I need to run a node to use a crypto wallet?

You do not need to operate your own node to use a cryptocurrency wallet. The vast majority of self-custody wallets connect automatically to remote nodes managed by commercial RPC providers or wallet developers. This default arrangement lets you send and receive tokens immediately without allocating local hard drive space or managing server processes. However, relying on public remote nodes means you trust an external service to report accurate balances and expose your network traffic to that provider. Advanced users often configure their wallets to communicate with a local private node to regain complete transaction privacy.

What is an archive node?

An archive node is a specialized full node that keeps every historical state of the blockchain starting from the genesis block and never deletes or prunes downloaded data. Standard full nodes verify the entire chain but periodically prune historical intermediate states once validated, keeping only recent state records to save disk space. Archive nodes preserve an exhaustive historical record of every balance, nonce, and contract storage slot at every past block height. Because they require massive storage capacity, archive nodes are primarily maintained by block explorers, data analytics platforms, and infrastructure services.

How do Ethereum execution and consensus clients work together?

A modern Ethereum node relies on two distinct software programs running concurrently: an execution client and a consensus client. The execution client executes smart-contract transactions, calculates gas, and manages the world state. The consensus client manages peer-to-peer networking, enforces Proof of Stake consensus rules, and handles block attestations. The two programs communicate locally through a local connection. When the consensus client receives a proposed block from the network, it passes the transactions to the execution client for execution, verifies the resulting state root, and updates the local chain tip.

Sources

Ready to put this into practice?

Exchange sign-up bonuses pay both you and a referrer after a qualifying trade.

See bonuses →