What it takes to be a Solana validator
Hardware, network, and cost of running a Solana consensus validator: Anza Agave requirements (CPU, RAM, NVMe, ports), bandwidth tiers, vote SOL burn, stake reality, and how this differs from an RPC node. Rough cost ranges and ops checklist.
devrels.xyz/a/216short linkRunning a Solana consensus validator means participating in voting and (with stake) leader slots — not serving public JSON-RPC. The bar is operational: keep a high-performance machine on a fat pipe, never empty the identity account that pays votes, and attract stake so the node is worth running.
Canonical requirements live in Anza’s Agave docs: Validator requirements, Validator vs RPC, Setup guide. Community hardware shortlist: solanahcl.org.
Consensus validator vs RPC node
| Consensus validator | RPC node | |
|---|---|---|
| Votes / earns protocol rewards | Yes (with vote account + stake story) | No |
| Primary user | The network (and your delegators) | Apps / traders hitting JSON-RPC |
| Hardware skew | CPU clock, disk IOPS, network | More cores/RAM, bigger ledger, indexes |
| Public RPC ports | Generally keep closed on mainnet stake | Open and scaled as a product |
This article is about consensus validators. RPC shops need the heavier column in Anza’s table and a different business model.
Hardware requirements
Anza publishes recommendations, not a single SKU. Operators are expected to benchmark. Summary of the official validator column:
| Component | Guidance |
|---|---|
| CPU | ≥2.8 GHz base; prefer higher clocks over more cores. SHA extensions; AMD Gen 3+ or Intel Ice Lake+. AVX2 for official binaries (else self-compile). AVX-512 helpful. 12 cores / 24 threads or more |
| RAM | 256 GB or more; ECC suggested; motherboard headroom toward 512 GB capacity is common planning |
| Disk | PCIe Gen3 x4 NVMe (or better), high TBW, preferably separate volumes: • Accounts — 1 TB+ • Ledger — 1 TB+ • Snapshots — 500 GB+ • OS — 500 GB+ optional (SATA OK) Accounts + ledger on one disk works but is not recommended under load |
| RPC extras | 16c/32t+, 512 GB+ RAM if full account indexes, larger ledger for history — not required for a pure voter |
Software: Agave targets Ubuntu 24.04. Prebuilt binaries have historically assumed x86_64 + AVX2; building from source is the durable path. Docker is not recommended for live cluster validators. Cloud VMs need serious tuning; Anza warns not to expect sympathy if you choose that path and struggle.
Second clients (e.g. Firedancer / Frankendancer) have their own preferred CPU layouts — see solanahcl categories before buying for a non-Agave stack.
Network requirements
| Item | Requirement |
|---|---|
| Addressing | Stable connection with a public IPv4 |
| Unstaked node | ~1 Gbit/s symmetric can be enough |
| Staked node | At least 2 Gbit/s symmetric; 10 Gbit/s available bandwidth recommended for stable operation |
| NAT | Not recommended; you own all debugging if you insist |
| Outbound | No filtering from validator to the internet |
Firewall
| Direction | Proto / ports | Notes |
|---|---|---|
| Required inbound | TCP + UDP 8000–8030 | Gossip, turbine, repair, etc. Remap with --dynamic-port-range if needed |
| Recommended | SSH (e.g. TCP 22) from your static management IP only | Lock down admin plane |
| Optional / caution | RPC 8899 / 8900 | Do not casually expose on staked mainnet validators |
Colocation next to other Solana operators and good peering matters as much as raw “up to 10G” marketing. Packet loss and jitter show up as skip rate and delinquency faster than a slow disk does.
SOL requirements
From Anza: there is no strict minimum amount of SOL to run an Agave validator on Solana. Practical floors:
| Item | Amount / note |
|---|---|
| Vote account rent-exempt reserve | About 0.02685864 SOL locked in the vote account |
| Voting fees | Up to about 1.1 SOL per day (docs also cite ~1.0 SOL/day) — paid from the validator identity account |
| Identity working balance | Keep a multi-day buffer (many operators hold tens of SOL+ so a refill outage does not halt voting) |
| Protocol minimum stake to exist | None — but without delegation you rarely cover costs |
| Economic stake | Rewards scale with active stake and performance (vote credits, leader slots). New validators usually need self-stake, SFDP/stake pools, or private delegation — plan this before buying iron |
Income side (high level): inflation rewards via vote credits; when leader, a share of transaction fees on produced blocks (protocol splits apply). Commission is your cut of staker rewards. Model with community tools (e.g. Cogent’s validator profit calculator) using your expected stake and commission — do not assume break-even at zero delegation.
Related builder context on stake mechanics: Solana staking.
Cost of the stack (order-of-magnitude)
Exact quotes move with CPU generations and colo markets. Use these as planning bands, then get current bids.
| Bucket | What you pay for | Ballpark |
|---|---|---|
| Server hardware | 12–32c class CPU (or Threadripper/EPYC), 256–512 GB ECC, 3–4× enterprise NVMe, NIC | Often mid four-figures to low five-figures to buy once; refresh cycle every few years |
| Colocation | Rack unit, power, remote hands | Hundreds of USD per month depending on power and facility |
| Bandwidth | 1–10 Gbit commit / burst, good transit | Can dominate opex at 10G; 1–2G is cheaper but staked mainnet wants headroom |
| Vote SOL | ~1–1.1 SOL/day at market price | Continuous opex in SOL terms — budget monthly at your price assumption |
| People / ops | On-call, upgrades, key ceremony, monitoring (agave-watchtower, paging) | Non-zero even for a “single box” — delinquency is a full-time failure mode |
| Optional | Spare parts, second location, Jito-Solana client ops, extra tooling | Adds both cost and complexity |
Bare metal in a Solana-dense colo still beats “random large cloud VM” for most serious operators. If you rent a managed validator bare-metal product, compare total monthly cost against self-build + colo + your time.
Skills and operations
- Linux performance tuning (disks, sysctl, CPU governor, NIC)
- Agave install/upgrade discipline aligned with cluster versions
- Key management: identity, vote authority, withdraw authority separation
- Monitoring and alerting — agave-watchtower and external explorers (e.g. validators.app)
- Stake marketing / SFDP or pool applications if you need external SOL
# Conceptual — not a full runbook
# 1) Ubuntu 24.04 bare metal, public IPv4, disks split
# 2) Install Agave / client of choice (see docs.anza.xyz)
# 3) Create identity + vote account; fund identity for votes
# 4) Open 8000-8030; lock SSH to admin IP
# 5) Start validator, wait for catchup, never empty identity
# 6) agave-watchtower --monitor-active-stake --validator-identity <PUBKEY>Checklist before you commit
- Consensus validator or RPC business? (Different box and P&L.)
- Hardware meets Anza floor; disks split; ECC RAM planned.
- Colo + ≥2 Gbit/s (prefer 10G headroom) + public IPv4, no flaky NAT.
- Vote rent + identity buffer for many days of ~1 SOL/day votes.
- Stake plan: self-stake and/or external delegation path.
- On-call and upgrade process before mainnet keys go live.
Related
- Agave requirements
- Solana HCL
- Solana staking
- Priority fees / Jito tips (leader fee context)
Summary
Becoming a Solana validator is mostly systems work: a fast multi-core machine with 256 GB+ RAM and serious NVMe, a public IPv4 path at multi-gigabit (10G recommended once staked), open P2P ports, and continuous funding of vote transactions at roughly a SOL per day. There is no protocol minimum stake, but without delegation the hardware and vote burn rarely make sense. Buy for IOPS and network first, keep RPC off the staked box unless you know why, and treat ops as part of the cost of securing the network.
Keep reading
Double the yearly drop in issuance — not half the supply overnight. One parameter change (-15% → -30% disinflation) to hit 1.5% terminal inflation years earlier.
NFC is a short-range radio tap. On Solana it usually means: phone reads a chip → app gets a URL or signed proof → on-chain mint, claim, or transfer. Here is the stack without the mystique.
Agave v4.2 branch cut June 29. Mainnet general adoption August 10. The headline: Anza is targeting 200ms slot times. The breaking changes: XDP transmit on by default (needs CAP_NET_ADMIN), blockstore legacy format removed, confidential transfer JSON fields renamed, vote-account CLI output changed.
Get new articles in your inbox
Technical deep-dives on Solana tooling, infrastructure, and ecosystem. No noise.
