Running a Solana validator is an infrastructure business with recurring SOL voting costs. Delegating SOL through Marinade Finance is a different activity: the stake owner earns rewards but does not operate consensus hardware. Before renting a server, model how much third-party stake you can attract and how much revenue you actually keep.
Anza's current Agave validator requirements and testnet setup guide are the sources to follow for commands, supported software and hardware. This article explains the decisions and the economics; exact network and market figures can change.
What a Validator Earns
A validator votes on blocks and may be selected as a leader to produce blocks. Its operator can receive:
- Commission on delegated staking rewards. Delegators own their stake and keep their rewards after the validator's stated commission. The operator receives only that commission on third-party stake.
- Rewards on the operator's own stake. These belong to the operator as a staker, whether they delegate to their own validator or another. Do not count the full reward on outside stake as operator income.
- Leader revenue. Base transaction fees, priority fees and potentially tips from a service such as Jito depend on actual leader slots and transaction demand. Solana's fee documentation says the base fee is split between burn and the leader, while priority fees go to the leader.
Against that revenue, budget vote fees, server and bandwidth bills, monitoring, staff time, outages and key-management costs. More delegated stake generally increases leader opportunities, but no fixed MEV percentage or monthly income is guaranteed.
Operators also contribute to network resilience. Geographic and client diversity matter, yet running another validator in the same data center does not automatically improve decentralization.
Hardware and Network: Use the Current Agave Baseline
Anza's requirements page recommends performance testing and currently lists the following starting points for a staked Agave validator:
| Component | Current guidance to verify before ordering |
|---|
| CPU | At least 12 cores / 24 threads, 2.8 GHz base clock, supported SHA and AVX2 instructions; clock speed matters |
| RAM | At least 256 GB; ECC is suggested and a motherboard supporting 512 GB leaves room to grow |
| Storage | NVMe for accounts and ledger, each 1 TB or more, plus snapshot space; separate high-endurance drives are preferred |
| Network | Public IPv4; at least 2 Gbit/s symmetric for a staked node, with 10 Gbit/s available bandwidth recommended |
| Operating system | Check Anza's currently supported Ubuntu and binary requirements |
These are guidance, not a warranty that a machine will keep up under every mainnet load. A dedicated RPC node with account indexes can need more resources than a voting validator. Anza advises against a standard Docker deployment for a live Agave validator because performance can suffer without special configuration.
Keep the public RPC ports closed unless you intentionally provide an RPC service. Anza lists the required peer-to-peer port range and treats RPC ports as optional; expose management access only to trusted IPs. Do not copy an old firewall recipe or storage layout into production without checking the current documentation.
Cost Model: Separate SOL and Fiat
Anza says there is no strict minimum SOL stake to run a validator, but a vote account needs a rent-exempt reserve and voting can cost up to about 1.1 SOL per day. That is an upper-bound planning input based on vote frequency, not a promise of what your node will spend. Your invoice for a suitable server, storage and connectivity is a separate fiat cost that depends on provider and location.
Prepare a spreadsheet with these inputs:
| Input | How to obtain it |
|---|
| Third-party delegated SOL | Confirmed stake or a cautious acquisition scenario |
| Own delegated SOL | Your capital, counted separately from outside stake |
| Realized reward rate and vote credits | Current epoch data and validator performance |
| Commission rate | Your vote-account setting and stake-pool terms |
| Leader fees and Jito tips retained | Actual historical receipts or a conservative zero estimate for a new node |
| Vote transactions and SOL fees | Observed votes per day and current fee schedule |
| Hosting, bandwidth and operations | Written provider quotes and monitoring plan |
For example, if 100,000 SOL of third-party stake earned a hypothetical 5% annual staking return and your commission were 5%, commission would be 250 SOL per year before other revenue and costs. The remaining staking rewards belong to delegators. At a hypothetical 1 SOL of vote fees per day, vote fees alone would be 365 SOL per year. Leader revenue may change the outcome, and the hosting invoice still needs paying. This illustrates why a table that treats all 100,000 SOL's staking rewards as validator income is wrong.
You can express the operator's approximate annual result as:
third-party stake × realized staking rate × commission
+ retained leader fees and tips
- vote fees
- hosting and operations converted at the SOL/USD rate actually paid
The operator's own staking rewards can be added to total household income, but compare them with the yield available from delegating that SOL elsewhere. Avoid counting them as a benefit unique to running the server.
There is no universal 50,000–100,000 SOL break-even threshold. It moves with commission, vote credits, leader fees, hardware invoices, SOL price and any stake-pool terms. Use our validator economics guide and validator rewards calculator as starting points, then replace every default with current observed data.