Some links on this page are affiliate links: if you buy through them we may earn a commission, at no extra cost to you.
A blockchain node is a computer—or virtual server—running software that connects to a blockchain’s peer-to-peer network and applies that network’s rules. Depending on its configuration, a node can receive and relay transactions, verify blocks, store blockchain data, maintain the latest state, provide data to applications, or participate in block production.
“Node” is a broad term. A full node is not automatically a miner or validator, an RPC endpoint is not necessarily infrastructure you control, and a wallet may rely on somebody else’s node. Understanding those distinctions helps you judge the security, privacy, cost, and convenience of different blockchain services.
A node’s job in one sentence
A blockchain node receives, verifies, stores, communicates, and exposes blockchain data according to protocol rules.
Wallet or application
↓
Node receives a transaction
↓
Node validates and relays it
↓
Miner or validator includes it in a block
↓
Nodes validate the block and update their stateA node is usually software running on a networked computer, not a special type of physical machine. One server can run multiple cooperating components, and one person can access a node without operating the underlying hardware.
#1 Best Overall
- Get NVMe solid state performance with up to 1050MB/s read and 1000MB/s write speeds in a portable, high-capacity drive(1) (Based on internal testing; performance may be lower depending on host device & other factors. 1MB=1,000,000 bytes.)
- Up to 3-meter drop protection and IP65 water and dust resistance mean this tough drive can take a beating(3) (Previously rated for 2-meter drop protection and IP55 rating. Now qualified for the higher, stated specs.)
- Use the handy carabiner loop to secure it to your belt loop or backpack for extra peace of mind.
- Help keep private content private with the included password protection featuring 256‐bit AES hardware encryption.(3)
- Easily manage files and automatically free up space with the SanDisk Memory Zone app.(5). Non-Operating Temperature -20°C to 85°C
Node, client, network, and protocol: what is the difference?
- Protocol: The rules defining valid transactions, blocks, state changes, and consensus.
- Client: A software implementation of those rules.
- Node: A running instance of client software participating in the network.
- Network: The collection of nodes following the same protocol.
For example, Geth is an Ethereum execution client. A server running Geth is an execution node. A complete post-Merge Ethereum setup normally combines an execution client with a consensus client, with an optional validator component. Ethereum documents this architecture in its node and client guide.
How a blockchain node processes a transaction
1. A wallet creates and signs the transaction
A wallet or application constructs a transaction and signs it with the relevant private key. The transaction might transfer coins, spend an unspent output, call a smart contract, or deploy contract code.
The wallet may send the signed transaction to a node it operates itself, to a hosted RPC service, or to infrastructure operated by an exchange or wallet company.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →2. The node checks the transaction
The exact checks depend on the blockchain, but a node may verify:
- Correct transaction format and size.
- Valid cryptographic signatures.
- Authority to spend the referenced assets.
- Sufficient funds or valid unspent transaction outputs.
- A valid nonce, where the blockchain uses account nonces.
- Fees, limits, and other protocol requirements.
- Whether the transaction conflicts with another transaction.
- Whether smart-contract execution succeeds, where applicable.
A transaction that passes these checks may enter the node’s mempool—a temporary pool of transactions waiting for inclusion in a block. The node can relay it to other peers. Mempool acceptance is not confirmation: the transaction is not yet part of the blockchain.
3. A miner or validator proposes a block
Block production depends on the consensus mechanism:
- In proof of work, miners compete to produce a block by performing computational work.
- In proof of stake, selected validators propose blocks and other validators attest to or vote on them.
- Permissioned and alternative blockchains may use designated or different consensus roles.
Most nodes do not produce blocks. They can still independently verify every block they receive.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
4. Nodes validate the proposed block
A receiving node checks the block’s structure and contents. Typical checks include:
- Whether the block points to an acceptable previous block.
- Whether the consensus proof or proposer authority is valid.
- Whether every included transaction is valid.
- Whether transactions conflict or spend the same funds improperly.
- Whether the block obeys size, fee, and protocol limits.
- Whether the resulting state transition is correct.
- Whether the block fits the network’s fork-choice rules.
If the block is invalid, the node rejects it and normally does not relay it as valid. Bitcoin Core full nodes, for example, use local validation rules to determine which chain is acceptable rather than simply trusting a server’s database. See the Bitcoin developer guide to the blockchain.
Rank #2
- Solid state performance with up to 800MB/s read speeds in a portable drive. (Based on internal testing; performance may be lower depending on host device, interface, usage conditions and other factors. 1MB=1,000,000 bytes.)
- Back up your content and memories on a storage solution that fits seamlessly into your mobile lifestyle.
- Take it with you on your adventures—up to two-meter drop protection means this durable drive can take a beating. (Based on internal testing.)
- Secure it to your belt loop or backpack for extra peace of mind thanks to the tough rubber hook.
- From Sandisk, a brand professional photographers trust to take on assignments.
5. The node updates its local state
After accepting a block, the node updates data such as the current chain tip, transaction records, unspent outputs or account balances, smart-contract state, receipts, and consensus information.
A blockchain is therefore more than a list of blocks. It is also a continuously updated state machine: each valid block changes the state according to deterministic rules.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →6. The node serves applications
Applications communicate with nodes through interfaces such as JSON-RPC, WebSockets, REST APIs, Bitcoin RPC, Ethereum execution APIs, and Beacon APIs. They can use these interfaces to:
- Read balances, blocks, transactions, and receipts.
- Estimate fees.
- Simulate smart-contract calls.
- Submit signed transactions.
- Subscribe to new blocks, events, and logs.
Ethereum’s execution clients expose JSON-RPC methods for querying the chain, submitting transactions, and interacting with smart contracts.
What does a node store?
Storage varies by blockchain, client, and configuration. A node may retain:
- Block headers and full blocks.
- Transactions and receipts.
- The current chain state.
- A temporary mempool.
- Wallet data and application-specific indexes.
- Historical state or tracing data.
It is inaccurate to say every node stores an identical complete copy of everything. A light client stores and verifies less data. A pruned full node can validate the chain while deleting older block data after validation. An archive node retains substantially more historical state or indexed historical information.
Recommended Free Tools
Blockchain node types compared
| Type | Independent validation | Historical data | Produces blocks? | Typical use |
|---|---|---|---|---|
| Light client | Limited or proof-based | Low | No | Phones, browsers, low-resource devices |
| Full node | Yes, according to protocol rules | Varies by client and configuration | Usually no | Verification, privacy, local access |
| Pruned full node | Yes | Deletes older data after validation | Usually no | Validation with lower storage needs |
| Archive node | Yes | Extensive historical state | Usually no | Analytics, indexing, historical queries |
| Validator | Yes, plus consensus duties | Depends on implementation | When selected | Proof-of-stake consensus |
| Miner | Usually uses validation software | Depends on setup | Through proof of work | Proof-of-work consensus |
| RPC service | Depends on its backend | Depends on its plan | Usually no | Application access |
Full nodes, archive nodes, and light clients
Full node
A full node independently validates blocks and transactions according to the blockchain’s rules. It generally retains enough information to verify current activity and maintain the current chain state.
“Full” does not necessarily mean “every historical state forever.” A pruned full node can remain a validating full node while removing older block files after they have been checked. Bitcoin’s documentation describes full nodes as downloading and checking blocks and transactions; see the official Bitcoin guidance.
Archive node
An archive node retains substantially more historical state or indexed data than a standard full node. It is useful for historical smart-contract queries, blockchain analytics, indexers, and debugging old executions.
Rank #3
- Easily store and access 2TB to content on the go with the Seagate Portable Drive, a USB external hard drive
- Designed to work with Windows or Mac computers, this external hard drive makes backup a snap just drag and drop
- To get set up, connect the portable hard drive to a computer for automatic recognition no software required
- This USB drive provides plug and play simplicity with the included 18 inch USB 3.0 cable
- The available storage capacity may vary.
Archive definitions differ between blockchains and clients, and archive operation can require much more storage and maintenance. Ethereum discusses full and archive infrastructure in its nodes-as-a-service documentation.
Light client
A light client uses fewer local resources and relies more on proofs, selected peers, or external infrastructure. It suits a phone, browser, or embedded device that needs basic verification without storing the full chain.
The trade-off is straightforward: lower storage and bandwidth requirements, but less complete local data and greater reliance on other infrastructure.
Validator, miner, wallet, and RPC node: the distinctions
Validator
A validator participates directly in a proof-of-stake consensus process. On Ethereum, the execution client handles transactions and state, the consensus client tracks consensus data and fork choice, and validator software performs duties such as attestations and block proposals.
Ethereum’s standard validator deposit model requires 32 ETH. That requirement applies to the validator role, not to every Ethereum node. A synced node without validator software can verify and relay data without proposing or attesting to blocks.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchMiner
A miner participates in a proof-of-work network by searching for a valid proof of work and proposing blocks. Mining hardware and node software are separate concepts: a normal full node can validate mined blocks without mining.
Wallet
A wallet is generally an interface and key-management tool. It may hold or use private keys while obtaining blockchain data from a remote RPC provider. Seeing a balance in a wallet does not prove that the wallet is independently validating the chain.
RPC node or RPC service
“RPC node” is usually an operational description, not a separate consensus category. It means a node or node-backed service exposed through an API.
The service may be self-hosted or provided by a company. It might offer a standard full node, archive data, tracing, logs, WebSockets, webhooks, or proprietary indexes. A hosted RPC endpoint is convenient, but you rely on the provider for availability, rate limits, privacy, data delivery, and correct configuration.
Rank #4
- NEARLY 2X FASTER THAN OUR PREVIOUS GENERATION(8) – move 1,000 high-res photos in under 60 seconds(6) with up to 2000MB/s transfer speeds(2).
- IP65 RATING AND UP TO 3M DROP PROTECTION(3) – protects against spills and drops.
- POCKET-SIZED – fits easily in pockets and small bags.
- SPACE TO OWN YOUR AI CONTENT – speed and capacity to download your high-res clips and photo edits.
- 256-BIT AES ENCRYPTION(4) – helps keep private files secure with password protection.
Bitcoin and Ethereum illustrate different designs
| Topic | Bitcoin | Ethereum |
|---|---|---|
| Typical software | Bitcoin Core | Execution client plus consensus client |
| Data model | UTXO-based | Account and state-based |
| Consensus example | Proof of work | Proof of stake |
| Block production | Mining | Validator proposals |
| Application access | Bitcoin RPC and related interfaces | JSON-RPC, WebSockets, Engine API, Beacon APIs |
Bitcoin
A Bitcoin Core full node validates transactions, scripts, blocks, and chain rules while maintaining information needed to track unspent transaction outputs. Miners produce proof-of-work blocks, but ordinary full nodes independently validate those blocks. Useful Bitcoin Core commands include:
bitcoin-cli getblockchaininfo
bitcoin-cli getnetworkinfo
bitcoin-cli getnettotals
bitcoin-cli getwalletinfo
bitcoin-cli stop
bitcoin-cli helpCurrent hardware and storage needs change over time, so consult the current Bitcoin full-node documentation rather than relying on old minimum figures.
Ethereum
A current Ethereum node normally consists of an execution-layer client and a consensus-layer client connected through a local authenticated Engine API. Validator software is optional unless the operator wants to perform staking duties. Common execution clients include Geth, Nethermind, Besu, and Erigon; consensus clients include Lighthouse, Prysm, Teku, Nimbus, and Lodestar.
Ethereum’s setup documentation gives this example for creating a shared JWT secret:
openssl rand -hex 32 > jwtsecretExact flags and storage requirements vary by client and change over time. Ethereum commonly recommends running the execution and consensus clients on the same machine in ordinary setups; its node-running guide covers the Engine API, JWT authentication, and operational considerations.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Why do nodes matter?
Independent verification
Running your own validating node reduces the need to accept a wallet company, exchange, block explorer, or RPC provider’s claim about what happened. Your software checks the data against the protocol’s rules.
Privacy
When you query a hosted provider, that provider may be able to associate addresses, balances, transaction broadcasts, and application activity with your IP address or account. A self-hosted node does not eliminate all privacy risks, but it can reduce reliance on a third-party query gateway.
Availability and censorship resistance
A provider can experience downtime, impose rate limits, delay a broadcast, or return incomplete data. Multiple independently operated nodes make the network less dependent on any one service.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errorsDecentralization
Decentralization is not simply a node count. Practical diversity also depends on geography, hosting-provider concentration, client diversity, bandwidth, hardware requirements, validator or miner concentration, and upgrade governance. A network with many nominal nodes hosted in one cloud region may be less resilient than the raw number suggests.
Best Value
- Easily store and access 5TB of content on the go with the Seagate portable drive, a USB external hard Drive
- Designed to work with Windows or Mac computers, this external hard drive makes backup a snap just drag and drop
- To get set up, connect the portable hard drive to a computer for automatic recognition software required
- This USB drive provides plug and play simplicity with the included 18 inch USB 3.0 cable
- The available storage capacity may vary.
Does running a node earn money?
Usually, no. A basic full node does not automatically receive rewards merely for validating and relaying data.
Rewards generally belong to specific roles, such as Bitcoin mining or proof-of-stake validation. A node operator might also earn money by selling RPC access or data services, but that is a business rather than an automatic protocol reward.
Running a non-rewarded full node can still provide independent verification, privacy, local transaction broadcasting, lower dependence on centralized RPC providers, and support for the peer-to-peer network.
Free tools Windows power users keep installed
One-click scans. No signup required.
Should you run your own node?
Run a full node when you:
- Need independent verification or better privacy.
- Operate a wallet, exchange, explorer, indexer, or financial application.
- Need predictable local access and control over configuration.
- Want to contribute to network resilience.
- Can maintain storage, bandwidth, updates, monitoring, and security.
Use a hosted RPC provider when you:
- Need to launch quickly or support multiple chains.
- Need elastic capacity, archive access, tracing, WebSockets, or webhooks.
- Do not want to operate infrastructure.
- Can accept provider outages, quotas, pricing, privacy trade-offs, and vendor dependence.
Use a light client when you:
- Have limited storage, bandwidth, or battery.
- Need basic verification rather than complete historical access.
- Accept some reliance on external peers or services.
Use an archive node when you:
- Need state at arbitrary historical block heights.
- Build analytics or indexing systems.
- Debug old smart-contract executions or require historical traces.
What operating a node involves
At a practical level, node operation includes:
- Installing compatible client software.
- Providing adequate disk space with growth headroom.
- Allowing sufficient CPU, memory, bandwidth, and synchronization time.
- Keeping software updated for protocol changes and security fixes.
- Monitoring synchronization, disk usage, peer connections, and service health.
- Protecting RPC interfaces and administrative credentials.
- Backing up important configuration and wallet data separately.
Cloud deployment can be convenient but may add recurring cost and increase dependence on a small number of infrastructure providers. Ethereum specifically notes that a censorship-resistant network should not rely entirely on cloud infrastructure.
Common failures and what they mean
- “Synced” but applications fail: RPC may be disabled, bound only to localhost, protected by authentication, missing required indexes, or behind the chain tip.
- Node will not sync: Check disk capacity, network connectivity, peer discovery, clock synchronization, client compatibility, and database health.
- Ethereum execution and consensus clients will not connect: Check the Engine API configuration and confirm both clients use the same JWT secret.
- Transactions appear missing: Confirm the correct network, chain ID, RPC endpoint, account, and block finality or confirmation status.
- RPC connection refused: Check whether the service is running, which interface and port it uses, firewall rules, and authentication.
- Publicly exposed RPC: Restrict access and require authentication. An unauthenticated administrative API can expose sensitive functions or allow abuse.
- Validator problems: Validator operation adds key-management, uptime, penalty, and slashing risks. A node can be useful without taking on those duties.
What happens if nodes disagree?
Temporary disagreement can result from network delays, competing blocks, forks, software bugs, configuration differences, protocol upgrades, or malicious data.
Consensus and fork-choice rules determine which block or chain is accepted. A node running incompatible software or the wrong network may follow a different chain. This is why client compatibility, upgrade timing, and correct configuration matter.
Independent validation also has limits: a node applies the rules implemented by its software and configuration. A software bug, compromised system, or incompatible protocol choice can still produce an incorrect result.
Recommended Free Tools
Bottom line
A blockchain node is a running participant in a blockchain protocol—not simply a computer holding a database. It communicates with peers, checks transactions and blocks, maintains local state, and may expose that data to applications.
Most nodes do not mine or validate blocks as a staking validator. The right choice depends on your goal: a light client minimizes resources, a full node maximizes independent verification, an archive node preserves deep historical data, and a hosted RPC service prioritizes convenience and scale. Running your own node reduces reliance on intermediaries, but it also brings storage, maintenance, security, and operational responsibilities.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
