Solana Mainnet Validator Operational Notes
Introduction (Purpose of this page)
In Solana, validators are not just operators of their own nodes.
They are a critical component that makes up the overall quality of the Solana chain.
They are a critical component that makes up the overall quality of the Solana chain.
When all validators operate at a high quality,
- Transactions are processed quickly
- Block production is stable
- The chain keeps running
- The user experience (UX) improves
As a result, the reliability of the Solana chain increases,
creating a positive cycle that attracts more users and use cases.
creating a positive cycle that attracts more users and use cases.
This is not only about “contributing to the network.”
Performance metrics actually affect stake pool evaluations and other assessments,
so high-quality validator operations also benefit the operator over time.
Performance metrics actually affect stake pool evaluations and other assessments,
so high-quality validator operations also benefit the operator over time.
With SLV, you can launch a Solana validator relatively easily,
and basic OS-level performance settings are applied automatically.
However, there are still key points that operators must understand and verify
to achieve stable performance in real-world operations.
and basic OS-level performance settings are applied automatically.
However, there are still key points that operators must understand and verify
to achieve stable performance in real-world operations.
This page summarizes common precautions for all mainnet validator operators
without depending on specific cases.
without depending on specific cases.
Check machine specs (based on official requirements)
For mainnet validators, you should plan for a configuration that can run stably
even during congestion, not just the bare minimum to start.
even during congestion, not just the bare minimum to start.
The following are guidelines based on official Solana / Agave / Firedancer documentation.
Agave Validator (official requirements and recommendations)
SOL requirements
- There is no strict minimum SOL requirement
- The Vote Account needs 0.02685864 SOL to be rent-exempt
- Voting transactions can cost up to ~1.1 SOL / day
Hardware requirements (guideline)
| Component | Validator | RPC Node (reference) |
|---|---|---|
| CPU | 2.8GHz+ / AMD Gen3+ / Intel Ice Lake+ / SHA extensions / AVX2 | 16 cores / 32 threads+ |
| RAM | 256GB+ | 512GB+ |
| Disk | NVMe Gen3 x4 or better / Accounts / Ledger / Snapshots separation recommended | Larger capacity recommended |
| GPU | Not required | Not required |
Note:
Clock speed and effective throughput are considered more important than core count.
Firedancer (Frankendancer)
Firedancer (Frankendancer) currently depends on Agave,
so at minimum it assumes the Agave recommended configuration or higher.
so at minimum it assumes the Agave recommended configuration or higher.
Minimum
- 24-core CPU @ >2.8GHz
- 256GB RAM
- 2TB NVMe (High TBW)
Recommended
- 32-core CPU @ >3GHz (AVX512 supported)
- 512GB RAM (ECC)
- Accounts / Ledger separation
- Network bandwidth of 1Gbps or higher
References:
Do not forget BIOS-level CPU Turbo / Performance Boost settings
The most important and most commonly overlooked point
is BIOS-level CPU Turbo / Performance Boost.
is BIOS-level CPU Turbo / Performance Boost.
In many environments,
people assume it is enabled by default,
but there are real cases where it is disabled in the BIOS.
people assume it is enabled by default,
but there are real cases where it is disabled in the BIOS.
If CPU Turbo is not enabled,
- Effective CPU performance drops below expectations
- Block production tends to be delayed
- Block time degradation may be observed
Validators with slow block production can be subject to penalties
in many stake pools and Solana Foundation programs.
in many stake pools and Solana Foundation programs.
Outline for checking BIOS settings
BIOS UIs differ by vendor,
but generally check the following items.
but generally check the following items.
- CPU Performance Boost / Core Performance Boost
- Turbo Mode / Turbo Boost
- Performance Profile (Performance rather than Power Saving)
SLV runs inside the OS and manages OS-level settings like CPU governor and pstate, but it cannot change BIOS or firmware settings.
Note:
BIOS settings cannot be checked from the OS.
When you bring up a new server or do an initial setup, always include BIOS verification in your checklist.
Check the kernel version (6.8.0 or higher recommended)
The Linux kernel is also an important factor for Solana validators.
As of January 2026, Kernel 6.8.0 or later is recommended.
It includes two updates that are important for Solana workloads.
It includes two updates that are important for Solana workloads.
How to check
Note: The kernel is often overlooked, but it directly affects CPU scheduling and I/O.
Check CPU settings (OS level)
OS-level CPU settings are important in addition to BIOS settings.
Make sure all of the following are in the performance state.
Energy Performance Preference (EPP)
CPU governor
amd_pstate (AMD CPU)
Note: If these are not satisfied, the CPU may run in power-saving mode and fail to deliver full performance.
In SLV, these are set by default,
but it is important to understand their meaning and verify them yourself.
but it is important to understand their meaning and verify them yourself.
What this page wants to tell you
The items listed here are not:
- special tuning
- advanced tips for experts
They are the minimum and essential checks
to prevent performance drops and unintended penalties,
even when operating with good intentions.
to prevent performance drops and unintended penalties,
even when operating with good intentions.
By checking these in advance, you can:
- achieve high-quality validator operations
- avoid unnecessary trouble
- contribute to improving the quality of the Solana network as a whole
Use this page as a checklist for real-world operations.