What is a crypto node?
If you searched "what is a node in blockchain," the answer is the same: a node is one participant in the network that holds the record and enforces its rules. "Crypto node" and "blockchain node" are used interchangeably.
A blockchain needs many nodes for the same reason an audit needs more than one auditor. Picture thousands of independent bookkeepers, each holding an identical copy of the books and the same rulebook. If one of them tries to slip in a bad entry, the others reject it. If one goes offline, the books survive everywhere else. That redundancy is what makes the record hard to censor or rewrite.
"Node" describes a role, not a kind of hardware. A laptop, a rack server in a data center or a rented cloud instance can all be nodes. What makes a machine a node is the software it runs and the network it joins.
Laptop
A home computer running a Bitcoin client
Data center
A rack server running a validator
Cloud
A rented instance serving storage
The same software on any of these makes the machine a node.
What does a blockchain node actually do?
Blockchain nodes perform different jobs depending on their role. Full nodes store and verify blockchain data, network peers relay transactions and blocks, and some service-oriented networks also use nodes to provide infrastructure such as storage or bandwidth.
Stores the ledger
A full node keeps the chain's data and the current state needed to check new activity. An archive node keeps everything from the first block onward. On Ethereum, archive data runs to units of terabytes, which is why most people run pruned full nodes.
Checks the rules
Every full node checks what it receives: valid signatures, enough funds, nothing spent twice, and correctly formed blocks. A node rejects invalid data no matter who sent it.
Relays data
Nodes pass new transactions and blocks to their peers, which pass them on again. This "gossip" spreads data across the network in seconds.
- Some networks
Serves useful work
Some networks ask nodes to store files, cache content close to users or carry bandwidth for real customers, and record proof that the work was done.
That fourth job is where most of the confusion about "running a node" comes from. Service nodes are covered in detail below.
How do crypto nodes work?
In six steps: a wallet signs a transaction, nodes pass it to their peers, each node checks it, a block producer includes it in a block, the network agrees on that block, and every node adds it to its copy of the ledger.
Signed and submitted
Your wallet signs the transaction with your private key and sends it to a node.
Gossiped to peers
That node passes it to its peers, and they pass it on, until most of the network has seen it.
Checked and queued
Each node verifies the signature, the balance and the format, then holds the valid transaction in its waiting area, often called the mempool.
Proposed in a block
A block producer (a miner or a validator, depending on the network) bundles waiting transactions into a new block.
- Where chains differ
Agreed by the network
The network runs its consensus process to accept the block.
Committed everywhere
Full nodes verify the accepted block, update their local chain data, and apply the resulting state changes.
Proof of Work (e.g. Bitcoin)
Miners compete to solve a costly puzzle, and nodes follow the chain with the most accumulated work.
Proof of Stake (e.g. CometBFT)
Validators take turns proposing a block, then vote on it in two rounds, prevote and precommit. The block is committed once validators holding more than two-thirds of the voting power precommit it, and a committed block is not replaced by a competing one. The design stays safe as long as validators with less than one-third of the voting power misbehave.
Where is a blockchain stored?
A blockchain is stored on every full node that runs it, not on one central server. Each full node keeps its own copy and checks it independently. Light clients, such as many mobile wallets, keep only block headers and ask full nodes for the rest, checking the answers against those headers.
Types of blockchain nodes, compared
Blockchain nodes split into types by how much they store and what role they play. The table compares the eight you are most likely to meet.
| Node type | What it does | What it stores | What it typically needs | Example networks |
|---|---|---|---|---|
| Full node | Checks every block and transaction, relays data | Recent chain data and current state | Disk, bandwidth, steady uptime | Bitcoin, Ethereum |
| Archive node | Everything a full node does, plus historical queries | All data and all past states | Several terabytes of fast storage | Ethereum (explorers, analytics) |
| Light node | Follows the chain and checks data it requests | Block headers only | Very little; runs on phones | Mobile and browser wallets |
| Miner | Competes to produce blocks in Proof of Work | A full copy of the chain | Specialized hardware and electricity | Bitcoin |
| Validator | Proposes and votes on blocks in Proof of Stake | A full copy of the chain | Locked stake that can be slashed, high uptime | Ethereum (32 ETH solo), Cosmos chains |
| RPC node | Answers requests from apps and wallets | Full or archive data | Capacity for heavy query traffic | Run by infrastructure providers |
| Masternode | Extra services such as instant or private transactions | A full copy of the chain | Fixed token collateral set by the network | Dash and similar networks |
| Service (operator) node | Delivers work customers use, and proves it | Whatever the service needs | Stake, bond or a license, per network | DePIN networks, including Sovren Network |
The difference between a full node and a light node is storage: a full node keeps and checks the chain itself, while a light node keeps block headers and asks full nodes for the rest.
Most full nodes on Bitcoin and Ethereum receive no protocol reward at all. People run them to verify the chain for themselves, to support apps they build, or to help the network stay decentralized.
Validators vs node operators: two jobs that get confused
Validators secure consensus and decide which blocks are final; service operators deliver work that customers use and prove it on-chain.
Here's what most people don't realize: on many newer networks, the node that validates blocks and the node that serves customers are different machines run under different rules.
| Validator | Service node operator | |
|---|---|---|
| What it provides | Block proposals and votes that secure the chain | Infrastructure such as storage, content delivery or bandwidth |
| What is at stake | Locked tokens that can be slashed | Whatever the network requires: a stake, a bond or a purchased license |
| What gets measured | Correct signing and participation in consensus | Work actually served, backed by verifiable proof |
| What can go wrong | Penalties for misbehavior or downtime; slashing for double-signing | Failed or disputed work, slashing where a stake is posted, low demand for the service |
In Proof of Stake networks, a blockchain validator node participates in consensus by proposing and voting on blocks. Its participation is generally backed by staked tokens, with specific requirements and penalties determined by each network. On Ethereum, a solo validator deposits at least 32 ETH, faces small penalties for being offline, and can be slashed for serious offenses such as double voting (ethereum.org, solo staking (opens in new tab)).
A service node operator is a newer role. The node's job is not to agree on blocks but to do work that someone outside the network asked for, then show evidence that it did.
Weighing either role? How to become a node operator
From ledger to infrastructure: what service nodes do differently
The difference between a validator and a service node is what gets measured: validators are judged on securing consensus, service nodes on work that customers actually use and that the network can verify.
Service nodes are the building blocks of decentralized physical infrastructure networks (DePIN). A DePIN uses a blockchain to coordinate real-world infrastructure, such as storage, content delivery, bandwidth, compute or wireless coverage, supplied by many independent operators rather than one company.
- A customer asks for a service
- A node does the work
- The network records proof
- Rewards follow verified work
Step 3 is what separates a service node from a machine that simply sits online. Networks use different methods, but the common ones are signed receipts for each request served, attestations in which other nodes confirm the work, and challenge or dispute windows during which bad claims can be contested and penalized. Without proof like this, a network cannot tell useful work from empty claims.
On-chain DePIN revenue, 2025
~$72M
DePIN sector value
~$10B
A service node only has work to do if customers want the service, and across the sector that demand is still small. Messari's State of DePIN 2025 report counted about $72 million in on-chain revenue across DePIN networks in 2025, against a sector valued at about $10 billion (Cointelegraph, January 2026 (opens in new tab)). Anyone looking at a service-node role should ask first who is paying for the work, and how much.
How does Sovren Network use nodes?
As of November 2026, Sovren Network uses two kinds of nodes: validators that secure consensus with CometBFT, and licensed operator nodes that support service markets including storage, CDN, bandwidth, and vector search. Operators receive SOVR for verified work under the network's rules.
Two node roles
Validators run CometBFT consensus, propose and vote on blocks, and keep the ledger final. Licensed operator nodes serve the network's service markets and are scored on verified work.
Service markets
Sovren Network supports storage, CDN (gateway), bandwidth, and vector search. GPU inference is also on the roadmap.
Proof
Each request an operator node serves produces a signed receipt, and the network scores that work over a rolling 30-day window.
Rewards
Operators receive the SOVR token for verified work under the network's rules. Rewards come from existing supply: minting is switched off at the chain level, and all 1,000,000,000 SOVR has existed since genesis.
Stack
A Cosmos SDK Layer 1 with 26 protocols. Mainnet chain ID sovr-1 produced its genesis block on 6 May 2026.
A node license is "for operating approved network infrastructure, not for investment purposes." Rewards depend on verified work and are not guaranteed, and you can lose money.
Sovren Network is operated by Sovren Technologies, "a vertically integrated digital infrastructure company building an independent technology ecosystem spanning social, streaming, commerce, payments, cloud, and decentralized infrastructure."
How to check a network's nodes yourself
In five checks: count the active validators, see how concentrated the stake is, check how many independent client implementations exist, look at missed blocks, and confirm that service work is recorded on-chain. Most of this takes ten minutes in a block explorer.
Active validator count
More independent validators generally means more resilience. A handful of validators means a handful of parties can coordinate.
Stake concentration
Find the smallest group of validators that together hold one-third of the voting power. In CometBFT-style consensus, that group can stall the chain, and two-thirds can finalize blocks on their own.
Client diversity
If every node runs the same software, one bug can affect them all at once. Networks with several independent implementations are harder to break.
Uptime and missed blocks
Explorers show which validators miss blocks or have been jailed. Frequent misses point to operational weakness.
Public proof of service work
On a service network, check whether receipts or attestations are visible on-chain, and whether the volume of work matches what the network claims.
For Sovren Network, the validator set and on-chain activity are visible on its public block explorer (opens in new tab). Apply the same five checks to any network you are considering, including Sovren.
What running a node involves
The short answer is that running a node means keeping a machine online, updated and secure, and for staked or licensed roles it also means putting money at risk.
- Hardware or hosting. A machine or rented server, steady bandwidth and enough storage for the chain to grow.
- Maintenance. Software updates when the network upgrades, monitoring so you know when the node falls behind, and careful handling of any keys it holds.
- Money at risk. Staked roles add the risk of penalties or slashing. Licensed roles add the cost of the license and any lockup on selling it.
Many node roles receive nothing at all, and none are guaranteed rewards. Our guide on how to become a node operator walks through the roles, requirements, costs, risks and steps.