What Validators Do All Day (And Why It Matters to Delegators)
A Solana validator runs specialised software on dedicated hardware, stays synchronised with the network, and submits votes on ledger progress. Each vote consumes a small amount of compute credits, and missed votes can reduce rewards for both the operator and their delegators.
Hardware requirements evolve as the network grows. Operators monitor CPU, memory, disk throughput, and network bandwidth. Downtime for maintenance is sometimes scheduled; unplanned outages are more concerning and visible in uptime statistics.
Validators also participate in cluster decisions indirectly by staying on the correct fork and applying software updates when new releases address bugs or performance issues. Falling behind on client versions can leave a validator voting on an obsolete chain state.
For delegators, this operational burden translates into metrics you can observe: skip rate, vote success, and epoch credit completeness. You do not need to administer a server, but recognising what operators manage helps you interpret those numbers.
In group sessions, we sometimes compare validator operation to running a small always-on business — fixed costs, uptime expectations, and reputation built over time. That analogy resonates with participants who have no prior server experience.
Want to discuss this topic live?
Our Staking Concepts Clinic covers questions like these in a 90-minute session.
Book a clinic