What does a node operator do?
A node operator keeps a blockchain node running so it can do its job for the network. If you need a refresher on the node itself, start with our guide to what a crypto node is.
Day to day, node operators are responsible for:
Uptime
Keeping the node running and connected, because a node that is offline cannot validate or serve anything.
Upgrades
Installing new software releases when the network changes its rules, often by a set date.
Monitoring
Watching sync status, disk space, memory and peer connections, and responding when something breaks.
Key security
Protecting the keys that control any stake, withdrawals or signing rights.
Governance
Voting on network proposals, where the role includes a vote.
Active work, not passive income. Even a managed setup leaves the operator with decisions, records and risk.
Which kind of node operator are you becoming?
The short answer is that there are four common operator roles (full or RPC node runner, Proof of Stake validator, staking-pool or delegated operator, and license-based DePIN operator), and each puts something different at risk. Choose the role before you choose the network or the token.
| Role | What you provide | What you put at risk | Technical load | How rewards are decided | Main downside |
|---|---|---|---|---|---|
| Full or RPC node runner | A machine that verifies the chain or answers app queries | Hardware and hosting costs | Medium to high | Usually no protocol reward; RPC providers charge customers | Costs with no on-chain income |
| Proof of Stake validator | Block proposals and votes | Your own staked tokens, which can be slashed | High | Protocol rules for proposing and attesting | Slashing, penalties, price exposure on locked stake |
| Staking-pool or delegated operator | Validator infrastructure for other people's stake | Reputation, delegated stake and any bond | High | Protocol rules, minus or plus the pool's fees | Answerable to delegators; slashing hits them too |
| License-based DePIN operator | Services such as storage, delivery or bandwidth | License price, any stake per market, capital locked by transfer limits | Low to medium | Verified work served, scored under the network's rules | Depends on real demand; license may not be sellable for months |
On Ethereum, for example, a solo validator must deposit 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)). Bitcoin full nodes sit in the first row: they receive no protocol reward, and people run them to verify the chain for themselves.
Three questions narrow the choice:
Do you have capital you can afford to lock up, and possibly lose?
If not, the validator and license rows are out.
Can you run and secure a server yourself?
If not, look at managed hosting or roles with a low technical load.
Do you have time to monitor the node every week?
Every row needs some; self-hosted validators need the most.
Node operator requirements: what you actually need
In five areas: hardware or hosting, network and uptime, stake or a license, key security, and the skills and time to maintain the node, plus any legal eligibility rules the network sets. How much each matters depends on the role you chose above.
Hardware and hosting
You have three options. Your own hardware gives you the most control but makes you responsible for power, cooling and repairs. A rented cloud or bare-metal server removes the physical work but adds a monthly bill and puts a hosting company between you and the node. A managed node-as-a-service provider runs the software for you, which costs more and leaves you trusting the provider with uptime and sometimes keys. Crypto node hosting is a crowded market, so compare terms, not just prices.
Network and uptime
Uptime matters differently by role. A validator that goes offline misses its turn to propose or vote and, on many networks, pays small penalties or is temporarily jailed. A service node that goes offline serves nothing, so it has no verified work to show. Check each network's rules on what counts as downtime and what it costs.
Stake, bond or license
These are three different things. A stake is tokens you lock up, which can be slashed if you break the rules. A bond is collateral posted against a specific service, returned if you perform. A license is a purchased right to operate a node, often issued as an NFT, which may carry a transfer lockup and comes with terms set by the issuer. Read which one a network requires, how long it is locked, and how you get it back.
Key and wallet security
Keep the keys that sign blocks or receipts separate from the keys that control withdrawals or funds. Store the most valuable keys on a hardware wallet or offline. Never run the same signing key on two machines at once: on many networks that is treated as double-signing, and a leaked or duplicated key can mean slashing or theft.
Skills and time
Self-hosted roles call for Linux administration, monitoring and disciplined upgrades. Managed and license-based roles need far less technical work, but they still need someone to watch the node's status, read network announcements and make decisions about stake, renewals and records.
Legal eligibility, KYC and tax
Some programs restrict who can take part by country, require identity checks (KYC) before you can claim rewards, or limit refunds. Read the operator agreement and terms of sale before you pay anything.
Tax rules differ by country. As one example, in the United States the IRS has ruled that a cash-method taxpayer includes staking rewards in gross income, at fair market value, in the year the taxpayer gains control of them (IRS Revenue Ruling 2023-14 (opens in new tab)). Rules for other reward types and other countries vary, so take advice where you live. This is not tax advice.
How to become a node operator in seven steps
In seven steps: choose a network and role, read its documentation and operator terms, budget the full cost, decide between self-hosting and a managed setup, secure your keys, deploy and register the node, then monitor and maintain it.
Choose a network and a role
Use the role table above. Decide what you are willing to put at risk and how much time you can give, then shortlist networks where that role exists. Pick the role before you pick the token: a role that does not fit your capital or skills will not be rescued by a promising network.
Read the documentation and the operator terms
Read the whitepaper, the technical documentation, the operator agreement and the terms of sale. Check that they agree with each other on the token name, total supply, lockups, vesting and what triggers penalties. Inconsistencies between documents are a reason to ask questions before you pay.
- Budget for zero
Budget the full cost
Add up the upfront cost, the recurring costs and the capital that will be locked, using the categories in the next section. Budget as if rewards were zero. If the plan only works when rewards arrive at a certain rate, it is not a plan you can rely on.
Decide between self-hosting and a managed setup
Self-hosting gives you control and keeps keys in your hands, at the cost of your time and skills. A managed provider saves time but adds a fee and a counterparty. Some programs support both; check which one the network expects for your role.
Secure your keys
Generate keys on a clean machine, back them up offline, and keep signing keys separate from withdrawal keys. Never run one signing key on two machines at once. Write down your recovery process before you need it.
Deploy, sync and register the node
This is where you set up the crypto node: install the client software, let it sync with the network, then register it. Depending on the role, registering means depositing stake, posting a bond or activating a license. Follow the network's own setup guide for the exact commands, and test on a testnet first if one exists.
Monitor, upgrade and take part in governance
Set up alerts for downtime, missed work and low disk space. Install client upgrades before the network's deadlines. Vote on proposals where your role includes a vote. Keep records of rewards received, dates and values for tax.
What it costs to run a node
The difference between the price of a node and its cost is everything that comes after: hosting, bandwidth, monitoring, and the capital that stays locked while you operate. Cost it in four categories.
| Category | What it includes | Questions to answer |
|---|---|---|
| Upfront | Hardware, a license purchase, or tokens for stake or a bond | Is any of it refundable? Can it be resold, and when? |
| Recurring | Hosting, bandwidth, electricity, monitoring tools, managed-service fees | What is the monthly total, and what if requirements rise? |
| Opportunity | Capital locked during transfer lockups, unbonding or vesting | How long until you could get your money out? |
| Risk | Slashing, token price changes, protocol changes, provider failure | What is the worst realistic loss, and can you absorb it? |
Cost the exit as well as the entry. Transfer lockups, unbonding periods and vesting schedules decide when money can leave, and that timing matters as much as the headline price.
The risks node operators carry
Here's what most people don't realize: the largest risks for a new operator are usually not technical. They are lockups that stop you selling, and token prices that move while you cannot.
- Slashing and jailing. Networks that use stake can destroy part of it for rule-breaking. On Cosmos SDK chains, the slashing module penalizes double-signing and downtime, and a jailed validator cannot propose or vote until it is released; delegators' stake is at risk too. Reduce it: never duplicate signing keys, and alert before a downtime threshold is reached.
- Downtime and missed work. An offline node receives nothing and may be penalized. Reduce it: reliable hosting, redundant power and network where you self-host, and alerts.
- Token price changes. Stake, bonds and rewards are usually denominated in the network's token, so their value can fall sharply while you operate. Reduce it: size your commitment to what you can afford to lose, and budget costs in your own currency.
- Lockups, unbonding and vesting. Licenses may be non-transferable for a period, staked tokens take time to unbond, and rewards may vest gradually. Reduce it: write down every lock period before you commit, and assume you cannot exit early.
- Protocol bugs and governance changes. Software bugs and governance votes can change rewards, requirements or penalties after you join. Reduce it: read the network's upgrade and governance history, and follow its announcements.
- Hosting-provider failure. A managed provider's outage or mistake becomes your problem. Reduce it: check the provider's track record and terms, and know how to move your node.
- Regulatory change. Rules for digital assets differ by country and can change. Reduce it: check the program's eligibility terms and take local advice.
Running a node can lose money. Rewards, where they exist, depend on verified work and the network's rules, and are not guaranteed.
The slashing and jailing rules above for Cosmos SDK chains come from the Cosmos SDK documentation (x/slashing) (opens in new tab).
How to become a Sovren node operator
The Sovren path has four steps: get your license, activate your node, register and serve the markets you choose, and receive SOVR for verified work.
Network
Sovren Network is a Layer 1 blockchain built with the Cosmos SDK and CometBFT consensus, with 26 protocols.
Your role
In the role table above, a Sovren operator is a license-based DePIN operator. Running a licensed operator node is a different job from running one of the CometBFT validators that secure consensus.
Licenses
10,000 in total
Transfer lockup
12 months from the purchase date
Vesting
Claimed SOVR vests linearly over 180 days
A node license is "for operating approved network infrastructure, not for investment purposes." Running a node is active work, not passive income, and you can lose money. Costs include hardware, bandwidth and electricity; staked SOVR can be slashed; the SOVR token's market price can fall; and protocol bugs or governance changes can affect operators. The license does not guarantee rewards, token value or any return.
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."
The Sovren path in four steps
As of November 2026, the Sovren node operator site (opens in new tab) describes the process this way:
Get your license
The license is NFT-backed and is the right to run a node on Sovren Network. Sovren says the license is "for operating approved network infrastructure, not for investment purposes."
Activate your node
The chain assigns workloads from the service markets the network needs. Sovren Network supports service markets including storage, CDN (gateway), bandwidth, and vector search. GPU inference is also on the roadmap.
Register and serve
Serving a market requires a stake of the SOVR token under that market's rules. You declare the markets you will serve, and requests are routed to your node.
Earn SOVR for verified work
Each request you serve produces a signed receipt. Work is scored over a rolling 30-day window, and the operator pool pays out daily according to that verified work. Rewards come from existing supply; no new SOVR is minted.
Key terms to know before you buy
- The license has a 12-month transfer lockup from the purchase date.
- Claimed SOVR vests linearly over 180 days.
- Sales are final and non-refundable except where the law requires otherwise.
- Hardware and hosting are separate costs. A license can run on managed infrastructure or on your own hardware.
- Staked SOVR can be slashed under the network's rules, for example for invalid or fraudulent work.
The full terms, including the license tiers, are in the node license key facts (opens in new tab) on the Sovren node operator site and in the Sovren Network whitepaper (v7.1). The way SOVR is issued and split is explained on the tokenomics page.
Questions to ask before you commit to any node program
The most useful question is the first one: who pays for the work these nodes do? If the answer is only new license buyers, the model depends on sales, not service. Ask every program these questions, Sovren's included, and get the answers in writing.
Who pays for the work nodes do?
Look for real demand for the services provided and understand how the network funds rewards.
Is the work provable on-chain?
Signed receipts or attestations let anyone check that work happened.
What exactly does the license or stake give me?
A right to operate is not ownership of the company or a claim on its revenue.
Is there a transfer lockup, and how long?
It decides when you could sell or exit.
How do vesting and unbonding work?
They decide when rewards or stake become usable.
What triggers slashing or penalties?
You need the exact rules, not a summary.
Who is eligible, and is KYC required to claim?
Some programs exclude certain countries or require identity checks later.
What is the refund policy?
Many node sales are final.
Do the whitepaper, operator agreement and sales page agree?
Token name, supply and terms should match in the whitepaper, operator agreement and sales page.
Is there an independent audit?
It shows that someone outside the team has checked the code or the token contracts.
Where can I see live network data?
An explorer or dashboard lets you verify claims yourself.